[jira] [Commented] (SOLR-9841) Disable expiration processor commits

["Hoss Man (JIRA)" <ji...@apache.org>]

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

Hoss Man commented on SOLR-9841:
--------------------------------

From my mailing list reply...

{quote}
The fact that there is no option prevent any commit at all was a concious 
choice:

a) the processor is basically useless unless something does a commit -- 
there's no point in doing deletes every 30 seconds if we only want to 
bother having a new searcher every 60 seconds -- it just means we're doing 
twice the work w/o any added benefit.

b) a softCommit+openSeacher is a No-Op unless there is soemthing to actauly commit. (see SOLR-5783 and TestIndexSearcher.testReopen)

{quote}

...there is no value add in a new option to prevent the commit from being fired -- it won't do anything unless there is something to commit.

If DocExpirationUpdateProcessorFactory users want commits to happen less frequently, then they can change the autoDeletePeriodSeconds to be less frequent, because by definition there is no utility in a low autoDeletePeriodSeconds value unless searchers are being re-opened with the same frequency.

----

bq. maybe this... is a Jira issue? Pretty unclear, having the menu item titled "Create Service Desk Request" when you're told to create a Jira issue...

sigh.  yes you did in fact create a jira issue -- aparently jira was upgraded recently and the term "Issue" doesn't seem to exist anymore, they appear to have been renamed into "Service Desk Request" ... i don't know why.

> Disable expiration processor commits
> ------------------------------------
>
>                 Key: SOLR-9841
>                 URL: https://issues.apache.org/jira/browse/SOLR-9841
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Brent Pearson
>
> http://lucene.472066.n3.nabble.com/Adding-DocExpirationUpdateProcessorFactory-causes-quot-Overlapping-onDeckSearchers-quot-warnings-td4309155.html
> Need a way to have document expiration update processor *not* trigger additional commits.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org