-
Type: Question
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.2.3
-
Component/s: Internal Code
-
None
Hi!
Resently,My mongodb server having 16 shardings which mongodb version is 4.2.3 for rhel7 x86_64 ,one of the 16 shardings throws error messages about mongodb 4.x verion's BUG SERVER-45119. As the BUG SERVER-45119 description ,we can refresh mongod's chunk version data using the command as "db.adminCommand({_flushRoutingTableCacheUpdates: ns, syncFromConfig: true})" trying to resolve the issue "requested shard version differs from config shard version". But I have five questions about the BUG SERVER-45119's "REMEDIATION AND WORKAROUNDS".
- Can I just refresh the chunk version data of the abnormal collection but refresh global mongod's chunk version data?
- Is the abnormal sharding beening locked if I use the command "db.adminCommand({_flushRoutingTableCacheUpdates: ns, syncFromConfig: true})" to refresh global mongod's chunk version data?
- Is my application's reading and writing beening affected before the completed of the command "db.adminCommand({_flushRoutingTableCacheUpdates: ns, syncFromConfig: true})" ?
- Is there other way to resolve the problem?
- How can I reproduce the scene of the BUG
SERVER-45119with mongodb 4.2.3 sharding for rhel7 x86_64? I was failed to reproduce the secene of the BUGSERVER-45119using method descriped inSERVER-45119.
- is duplicated by
-
SERVER-53346 The best method resolving BUG SERVER-45119 of mongodb 4.2.3 for rhel7 x86_64
- Closed
- related to
-
SERVER-45119 CollectionShardingState::getCurrentShardVersionIfKnown returns collection version instead of shard version
- Closed