[SERVER-18437] Improve Concurrency of Sharding registry Created: 12/May/15  Updated: 05/Feb/16  Resolved: 17/Jun/15

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

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

Issue Links:
Gantt Dependency
has to be done after SERVER-18049 Move staticShardInfo out of shard.cpp Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 3 05/15/15, Sharding 4 06/05/15, Sharding 5 06/26/16
Participants:

 Comments   
Comment by Githook User [ 17/Jun/15 ]

Author:

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

Message: SERVER-18464/SERVER-18437/SERVER-19004 Move targeter ownership to Shard

Currently there is a discrepancy between the ownership of the targeter
object and the lifetime of Shard. It is possible that if a shard has been
created and a targeter disappears then operations on that shard will not
find the targeter.

This change moves the ownership of targeter to the Shard object itself.
Branch: master
https://github.com/mongodb/mongo/commit/6584bfd3ddcdb1598fb486615c49f0272798f5d6

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