-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
ALL
-
Cluster Scalability 2024-11-11
While adding a new core_sharding test for moveCollection for SERVER-94914, the command "find({}).itcount()" is returning 0 when in fact it should have received an error from the server. Mongos is in fact getting a StaleConfig error and refreshes.
[j0:s] {"t":{"$date":"2024-11-06T18:10:59.549+00:00"},"s":"I", "c":"QUERY", "id":4625501, "svc":"R", "ctx":"conn28","msg":"Unable to establish remote cursors","attr":{"error":{"code":13388,"co deName":"StaleConfig","errmsg":"timestamp mismatch detected for test.move_collection_capped_collection","ns":"test.move_collection_capped_collection","vReceived":{"e":{"$oid":"000000000000000000000000"},"t":{"$timestamp":{"t":0,"i":0}},"v":{"$timestamp":{"t":0,"i":0}}},"vWanted":{"e":{"$oid":"672bb133611e746c1f1680ae"},"t":{"$timestamp":{"t":1730916659,"i":1110}},"v":{"$timestamp":{"t":0,"i":0}}},"shardId":"shard-rs1"},"nRemotes":0}}
- depends on
-
SERVER-97219 [test-only bug] Don't use randomize data shard for createCollection if registerExistingCollectionInGlobalCatalog is set
- Open
- related to
-
SERVER-97249 Complete TODO listed in SERVER-96790
- Backlog
-
SERVER-94914 Develop core_sharding tests for movePrimary
- Closed