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 2014/12/05 16:53:17 UTC

[jira] [Created] (LUCENE-6094) IW.rollback can take forever when CMS has stalled threads

Michael McCandless created LUCENE-6094:
------------------------------------------

             Summary: IW.rollback can take forever when CMS has stalled threads
                 Key: LUCENE-6094
                 URL: https://issues.apache.org/jira/browse/LUCENE-6094
             Project: Lucene - Core
          Issue Type: Bug
          Components: core/index
            Reporter: Michael McCandless
            Assignee: Michael McCandless
            Priority: Minor
             Fix For: 5.0, Trunk


CMS hard-stalls incoming threads for denial-of-service protection when merging cannot keep up with whatever is producing new segments.

When you call IW.rollback, it asks all merges to abort, and a running merge will periodically check to see if it should abort.

However, a stalled merge fails to check, which means rollback can take indefinitely long; I've seen this in Elasticsearch causing shutdown to take > 10 sec.



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