[SERVER-21185] Make shard primary responsible for updating config server's knowledge of shard replica set members Created: 22/Oct/15  Updated: 06/Dec/23  Resolved: 06/Dec/23

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

Type: Improvement Priority: Major - P3
Reporter: Crystal Horn Assignee: Wenqin Ye
Resolution: Fixed Votes: 0
Labels: AdiZ, sharding-common-backlog, sharding-nyc-subteam3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Cluster Scalability 2023-12-11
Participants:
Linked BF Score: 0
Story Points: 3

 Description   

Currently, when a shard replica set is reconfigured to add or remove nodes, all mongoses monitoring that set will detect the change and each one will attempt to update the seed list for that set that is stored on the config servers. This means all the mongoses are racing to do the update, performing duplicate and unnecessary work and network traffic. Instead, the primary of the set being reconfigured should be the sole party responsible for updating the configuration stored on the config servers.



 Comments   
Comment by Githook User [ 06/Dec/23 ]

Author:

{'name': 'Wenqin Ye', 'email': 'wenqin908@gmail.com', 'username': 'wenqinYe'}

Message: SERVER-21185 Make shard primary responsible for updating config server's knowledge of shard replica set members

GitOrigin-RevId: a31db4e9df35f2cfb88713d3771e60b9c7412135
Branch: master
https://github.com/mongodb/mongo/commit/3a61c3f327efb5b5c4b1646febddd658b15aafad

Comment by Githook User [ 16/Sep/23 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: Revert "SERVER-21185 Make shard primary responsible for updating config server's knowledge of shard replica set members"

This reverts commit 1eb2c72f85f1ee9ec74a081003a2ab1c0d305bfd.
Branch: master
https://github.com/mongodb/mongo/commit/9adc7952e55fe149efb5300554d0eaba0d1f23f2

Comment by Githook User [ 05/Sep/23 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-21185 Make shard primary responsible for updating config server's knowledge of shard replica set members
Branch: master
https://github.com/mongodb/mongo/commit/1eb2c72f85f1ee9ec74a081003a2ab1c0d305bfd

Comment by Adi Zaimi [ 31/Jan/23 ]

TODO: Is this tkt still applicable, ie. is it still the case that all mongoses try to do the update?

Generated at Thu Feb 08 03:56:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.