[SERVER-27364] Remove DBConfig::setPrimary Created: 09/Dec/16  Updated: 05/Apr/17  Resolved: 17/Dec/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.1
Fix Version/s: 3.4.2, 3.5.2

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-20854 Don't refresh database and collection... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: Sharding 2017-01-02
Participants:

 Description   

The DBConfig::setPrimary method does a write under the database cache entry's mutex. It is only used as part of the movePrimary command and is better if it resides there and run outside of the mutex.



 Comments   
Comment by Githook User [ 03/Jan/17 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-27364 Remove DBConfig::setPrimary

Moves its entire functionality to the 'movePrimary' command.
Branch: v3.4
https://github.com/mongodb/mongo/commit/499014391364d74b8ee143e2a9685460ba2a1978

Comment by Githook User [ 17/Dec/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-27364 Remove DBConfig::setPrimary

Moves its entire functionality to the 'movePrimary' command.
Branch: master
https://github.com/mongodb/mongo/commit/caba732fb722d5c2257d17dd09dec8a826c13795

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