[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-453) FSSlaveDirectoryProvider: initial refresh

[Stephan Bublava (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35474#action_35474 ] 

Stephan Bublava commented on HSEARCH-453:
-----------------------------------------

The copy in start() is only performed, if there is no marker file present.

In my case the refresh period was simply much too large, so copying immediately would have made a noticeable difference. I've fixed the configuration and suggest to close this ticket.

Thanks,
Stephan


> FSSlaveDirectoryProvider: initial refresh
> -----------------------------------------
>
>                 Key: HSEARCH-453
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-453
>             Project: Hibernate Search
>          Issue Type: Improvement
>          Components: directory provider
>    Affects Versions: 3.1.1.GA
>            Reporter: Stephan Bublava
>            Priority: Minor
>
> FSSlaveDirectoryProvider schedules the first refresh of the index files after the defined refresh period has elapsed. The first refresh should occur immediately.
> In other words:
>     TimerTask task = new TriggerTask( sourceIndexDir, indexDir );
>     long period = DirectoryProviderHelper.getRefreshPeriod( properties, directoryProviderName );
>     timer.scheduleAtFixedRate( task, 0L, period );
> instead of:
>     TimerTask task = new TriggerTask( sourceIndexDir, indexDir );
>     long period = DirectoryProviderHelper.getRefreshPeriod( properties, directoryProviderName );
>     timer.scheduleAtFixedRate( task, period, period );

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira