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

Improve how ConcurrentMergeScheduler handles too-many-merges case

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 2.3
    • 2.4
    • core/index
    • None
    • New

    Description

      CMS now lets you set "maxMergeThreads" to control max # simultaneous
      merges.

      However, when CMS hits that max, it still allows further merges to
      run, by running them in the foreground thread. So if you set this max
      to 1, and use 1 thread to add docs, you can get 2 merges running at
      once (which I think is broken).

      I think, instead, CMS should pause the foreground thread, waiting
      until the number of merge threads drops below the limit. Then, kick
      off the backlog merge in a thread and return control back to primary
      thread.

      Attachments

        1. LUCENE-1164.patch
          4 kB
          Michael McCandless

        Activity

          People

            mikemccand Michael McCandless
            mikemccand Michael McCandless
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: