Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
None
-
ALL
-
Sharding EMEA 2022-08-08, Sharding EMEA 2022-08-22, Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31
-
0
Description
CollectionMetadata offers a method to get a weak reference to the chunk manager it points to.
It has been observed a case in which this led to the chunk manager being cleared up while still used by an op observer.
The flow that led to hit the error - right after a refineCollectionShardKey was the following:
- The application of an insert oplog entry on a secondary triggered ShardServerOpObserver::onInserts (yes, the observer is also active on secondaries)
- incrementChunkOnInsertOrUpdate got called with a pointer to the old chunk manager as argument, and succeeded to get the old shard key
- Upon calling findIntersectingChunkWithSimpleCollation, the chunk manager got cleared up (because the pointer was not shared) and the chunk info was not found
Attachments
Issue Links
- depends on
-
SERVER-70758 Stop tracking chunk writes in versions supporting data-size aware balancing
-
- Closed
-