[SERVER-53338] The best method resolving BUG SERVER-45119 of mongodb 4.2.3 for rhel7 x86_64 Created: 13/Dec/20  Updated: 03/Jun/22  Resolved: 15/Jan/21

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: 4.2.3
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Jing Feng Assignee: Eric Sedor
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-53346 The best method resolving BUG SERVER... Closed
Related
related to SERVER-45119 CollectionShardingState::getCurrentSh... Closed
Participants:

 Description   

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".

  1. Can I just refresh the chunk version data of the abnormal collection but refresh global mongod's chunk version data?
  2. 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?
  3. Is my application's reading and writing beening affected before the completed of the command "db.adminCommand({_flushRoutingTableCacheUpdates: ns, syncFromConfig: true})" ?
  4. Is there other way to resolve the problem?
  5. How can I reproduce the scene of the BUG SERVER-45119 with mongodb 4.2.3 sharding for rhel7 x86_64? I was failed to reproduce the secene of the BUG SERVER-45119 using method descriped in SERVER-45119.


 Comments   
Comment by Eric Sedor [ 15/Jan/21 ]

Hi fengjing@vastdata.com.cn,

The best approach to SERVER-45119 at this point is to upgrade to 4.2.6 to avoid the issue altogether. That is what we recommend.

Beyond that, if it is truly necessary for you to explore this, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums.

There, you can get clarifications on how MongoDB works and suggestions for how to approach particular problems. If you post there explaining some context about why you need to reproduce SERVER-45119, they should be able to provide insight.

If the discussion there leads you to suspect a bug in the MongoDB server, or an inaccuracy in what we've documented at SERVER-45119, then we'd be able to address this here in the SERVER project (which is for reporting bugs and feature suggestions for the MongoDB server).

Hopefully this helps,
Eric

Generated at Thu Feb 08 05:30:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.