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

Recipient shard should not wait for `orphanCleanupDelaySecs`

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • Sharding 2017-12-18, CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19
    • 3

      The orphanCleanupDelaySecs parameter was added as part of the "secondaries chunk-aware" feature, so that chunk migration on a shard primary does't immediately rip-out documents from underneath queries running on the secondaries.

      It essentially has the same effect as if a cursor was open for 15 minutes on a donating shard's primary. Because of this, receiving a chunk back would block for up to 15 minutes. This is a change in behavior between 3.4 and 3.6. In the same situation. In this case 3.4 would have wiped out the range from underneath the active queries.

      We should preserve the 3.4 behaviour.

            Assignee:
            Unassigned Unassigned
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            4 Vote for this issue
            Watchers:
            46 Start watching this issue

              Created:
              Updated: