msokolov commented on issue #14431: URL: https://github.com/apache/lucene/issues/14431#issuecomment-2781449497
We're operating in a setup where we have an initial phase that builds an index while it is offline, not accepting query traffic. Once that is complete, we enable the index to take queries, and it continues to receive updates. We would like to allow the initial phase to proceed with minimal merge activity, then run forceMergeDeletes , and then proceed to bring the index on line. If forceMergeDeletes fails to complete in a timely fashion, we need to go ahead and bring the index online regardless. Agreed, that no deletions will have been merged away at that point, but they will eventually, and we would rather suffer with an index having a high delete ratio for some time than sacrifice the bounded time window (that we can usually live within). Basically the timeout will give us a bound on the worst case merge time. I think in general whenever we one provides a blocking API it's good practice to offer a version with a timeout so that callers can have some control over whether to term inate, keep waiting, or perhaps allow it to continue running in the background. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
