-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.4.14
-
Component/s: Sharding
-
None
-
Environment:2 shards, 3 config servers
-
Sharding
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
If mongos detects that config servers are different, metadata should not be changed.
- Ongoing split/moveChunks operations can lead to the full inconsistency if the first config is corrupted for some reason;
- Ongoing metadata changes can mask the original issue
I checked manually with 2.4.1, and I could do manual splitAt and moveChunk, while my second config server was out of sync.