[SERVER-32375] Config metadata commands should not use readConcern majority Created: 15/Dec/17  Updated: 30/Oct/23  Resolved: 10/May/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.1
Fix Version/s: 4.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-31414 The writes of _configsvrEnableShardin... Closed
is duplicated by SERVER-33256 shardCollection gets DuplicateKeyErro... Closed
Related
related to SERVER-37929 ShardRegistry in config servers can k... Closed
is related to SERVER-30559 Sharding tests which run under contin... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-04-09, Sharding 2018-04-23, Sharding 2018-05-07, Sharding 2018-05-21
Participants:
Linked BF Score: 20

 Description   

For example, in removeShard command it get trigger a ShardRegistry refresh, but it uses the same operation context to do a readConcern majority read, and this can cause some weird behavior because the command will think that shards exists, when in fact they no longer do.



 Comments   
Comment by Githook User [ 10/May/18 ]

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-32375 Use readConcern local for config metadata operations
Branch: master
https://github.com/mongodb/mongo/commit/ec4a3883899f3ea9f4600b786596f0b17fd00106

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