[SERVER-51789] Execute the getShardAndCollectionVersion function before logging which chunks were created in the split chunk operation Created: 21/Oct/20  Updated: 29/Oct/23  Resolved: 23/Oct/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Bug Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: sharding-csrs-stepdown-only, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:
  • Reduce the interval time between stepdowns
  • Run the mongos_get_shard_version.js from the sharding_csrs_continuous_config_stepdown suite and check the logs to see if the split chunk failed
Participants:
Linked BF Score: 24

 Description   

The underlying problem here is that the split chunk operation is not idempotent.
Instead of fixing that, what we try to achieve with this change is reducing the probability of having an error during the split chunk operation.

The change is simple: we have to moveĀ  this call before this region of code



 Comments   
Comment by Githook User [ 23/Oct/20 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-51789 Execute the getShardAndCollectionVersion function before logging which chunks were created in the split chunk operation
Branch: master
https://github.com/mongodb/mongo/commit/f5ece56753374c4c38f998fde7402a690aea8fff

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