-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.4.18, 3.6.9
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
v4.2, v4.0
-
-
Sharding 2019-09-09
-
(copied to CRM)
We've noticed that after removing a shard, fanout queries (e.g. issue a collection count against a sharded collection) will return ReplicaSetMonitorRemoved or ShardNotFound errors. While investigating, it looks like the internal chunk cache has an old config (getShardVersion on the collection returns an old version). It appears that as long as no non-fanout queries (or inserts/removes) are issued after the remove has completed, fanout queries on some mongos have a relatively high chance of consistently failing.
- is duplicated by
-
SERVER-18175 Chunk manager references removed shard, if it was tagged
- Closed
-
SERVER-30701 ChunkManager can contain chunks that refer to shards that were removed
- Closed
-
SERVER-46752 moveChunk will keep on returning ShardNotFound until DatabaseVersion is updated
- Closed
- is related to
-
SERVER-43197 Improve testing for ShardRegistry reload invalidating CatalogCache on shard removal
- Closed
- related to
-
SERVER-39205 Force the cache refresh after the shard is removed.
- Closed
-
SERVER-40709 CatalogCache should mark database entry as needs refresh on encountering ShardNotFound when trying to get primary shard's Shard object
- Closed