incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Spicar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLEREZZA-564) CRIS: call optimize in an extra thread
Date Wed, 22 Jun 2011 08:24:47 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053120#comment-13053120
] 

Daniel Spicar commented on CLEREZZA-564:
----------------------------------------

Lucene does already run merge in extra threads internally. A non-blocking call can be ensured
using the optimize(boolean doWait) method when using the ConcurrentMergeSheduler (default).

However care should to be taken, to not close the Writer while a merge is running.

> CRIS: call optimize in an extra thread
> --------------------------------------
>
>                 Key: CLEREZZA-564
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-564
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Tsuyoshi Ito
>
> Comment from Tommaso (see http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201106.mbox/%3CBANLkTimtPvGC3M6uW94mo1xf=eU-DYLYcA@mail.gmail.com%3E)
> A possible enhancement could be to create an OptimizeThread with a timeInterval constructor
which optimizes the index, if there is not "much" activity (i.e.: analyze isLocked, InfoStream,
etc), every timeInterval seconds.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message