Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-6094

IW.rollback can take forever when CMS has stalled threads

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.10.3, 5.0, 6.0
    • Component/s: core/index
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      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.

        Attachments

        1. LUCENE-6094.patch
          4 kB
          Michael McCandless

          Activity

            People

            • Assignee:
              mikemccand Michael McCandless
              Reporter:
              mikemccand Michael McCandless
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: