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

Do not wait for range deletion thread on stepdown

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • Affects Version/s: 6.2.0-rc0
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Hide

      Apply the provided patch on top of r6.2.0-alpha-1295-gab34541c92e and run:

      resmoke.py --suite=sharding jstests/sharding/range_deletion_hang_stepdown.js
      
      Show
      Apply the provided patch on top of r6.2.0-alpha-1295-gab34541c92e and run: resmoke.py --suite=sharding jstests/sharding/range_deletion_hang_stepdown.js
    • Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14
    • 55

      On stepdown the RangeDeleterService destruct the ReadyRangeDeletionsProcessor that in turns interrupt and join its internal thread.

      In order not to slowdown the stepdown process we should instead

      • Interrupt the internal thread onStepDown()
      • Join the internal thread onStepUpBegin()
      • Start the internal thread onStepUpComplete

      The proposed approach will still guarantee that all the previous range deletions will be drained strictly before the node can transition to PRIMARY again.

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: