Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-95674

Introduce configurable time limit to scan chunks during auto-merging

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: 7.0.9, 7.3.4, 8.0.2
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0
    • CAR Team 2024-11-11, CAR Team 2024-11-25, CAR Team 2024-12-09
    • 200
    • 2

      MergeAllChunksOnShard runs optimistically and retries immediately if a conflicting moveChunk committed concurrently, up to 5 times. After that we fail the command with ConflictingOperationInProgress. This is detected by the AutoMergerPolicy which re-schedules the merge action immediately.

      In a situation where moveChunks are constantly committing this drives up CPU utilization, specially while SERVER-78701 hasn't been fixed.

      We should reduce the likelihood of merge chunks and move chunks being concurrently running for the same namespace.

            Assignee:
            silvia.surroca@mongodb.com Silvia Surroca
            Reporter:
            daniel.gomezferro@mongodb.com Daniel Gomez Ferro
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: