-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Labels:None
-
Catalog and Routing
-
Sharding 2017-12-18, CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19
-
(copied to CRM)
-
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 behaviour 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.
- depends on
-
SERVER-29344 Inform queries on a secondary node when the range deleter starts cleaning-up ranges on the primary
-
- Closed
-
- has to be done after
-
SERVER-87673 Queries which run on secondaries and exceed orphanCleanupDelaySecs may miss documents which were donated by chunk migration
-
- Needs Scheduling
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Needs Scheduling
-
-
SERVER-29405 After move chunk out, pause for secondary queries to drain
-
- Closed
-