-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Sharding EMEA 2022-07-11
The notifySecondariesThatDeletionIsOccurring function is writing on disk to supposedly notify secondary nodes when a range deletion is starting.
However, there is no observer on secondaries reacting to the write. Traced back this problem at least down until v4.4, so secondaries have never been notified in recent versions.
Purpose of this ticket is to simply get rid of the function since it has never done what it claims to.
- is related to
-
SERVER-67385 Range deletion tasks may be wrongly scheduled before ongoing queries on range finish on a shard primary
- Closed
-
SERVER-68352 Only wait for `orphanCleanupDelaySecs` before allowing range deletion to start
- Closed
- related to
-
SERVER-87673 Queries which run on secondaries and exceed orphanCleanupDelaySecs may miss documents which were donated by chunk migration
- Backlog