[SERVER-66338] Donor has multiple errors resuming a shard split in the blocking state Created: 10/May/22  Updated: 29/Oct/23  Resolved: 11/May/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Matt Broadstone Assignee: Matt Broadstone
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

A number of issues identified by implementing shard split stepdown passthroughs:

  • Waiting for recipient nodes to reach block timestamp doesn't work because no recipient nodes are listed in local members after applying the split config
  • Similarly, we attempt to rebuild a recipient connection string after a split config has been installed, which is impossible since the recipient nodes have been removed from the local member list
  • Installing a split config on top of a pre-existing split config may result in strange replication errors ("installed the config, but unable to get majority commitment")


 Comments   
Comment by Githook User [ 11/May/22 ]

Author:

{'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}

Message: SERVER-66338 Skip blocking steps if split config already applied
Branch: master
https://github.com/mongodb/mongo/commit/8ab35fa86b4d299c672f362311330abbd7c6f8b1

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