You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2015/06/17 17:39:01 UTC

[jira] [Created] (LUCENE-6579) Unexpected merge exceptions should be tragic to IndexWriter

Michael McCandless created LUCENE-6579:
------------------------------------------

             Summary: Unexpected merge exceptions should be tragic to IndexWriter
                 Key: LUCENE-6579
                 URL: https://issues.apache.org/jira/browse/LUCENE-6579
             Project: Lucene - Core
          Issue Type: Bug
            Reporter: Michael McCandless
            Assignee: Michael McCandless
             Fix For: 5.3, Trunk


Today our behavior is weird: we will fail the merge (which is running in a background thread if you are using the default CMS), pause for 1.0 seconds, and then the next chance we get, kick off the merge again.

I think this is a poor default, e.g. on disk full we will just keep "trying" and filling up disk again, wasting IO/CPU.

I think IW should declare this a tragedy instead?



--
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