[SERVER-25105] add OpObserver for deletes to config.shards to cancel corresponding upsertShardIdentityForAddShard task Created: 15/Jul/16  Updated: 13/Aug/16  Resolved: 27/Jul/16

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 17 (07/15/16), Sharding 18 (08/05/16)
Participants:

 Comments   
Comment by Githook User [ 27/Jul/16 ]

Author:

{u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}

Message: SERVER-25105 fix lint
Branch: master
https://github.com/mongodb/mongo/commit/8921bd532db423bc50e65975663a4438e86d3fd8

Comment by Githook User [ 27/Jul/16 ]

Author:

{u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}

Message: SERVER-25105 add OpObserver for deletes to config.shards to cancel corresponding upsertShardIdentityForAddShard task
Branch: master
https://github.com/mongodb/mongo/commit/f0c7b01ab26b6ac7ba555070819aaa0f5a7ddee0

Comment by Esha Maharishi (Inactive) [ 15/Jul/16 ]

We could potentially not do this. By not doing it, a removeShard by a legacy mongos would not delete the shardIdentity doc.

The shard would be able to re-join the same cluster (once addShard idempotency is implemented fully).

The shard would not be able to join a different cluster until the shardIdentity doc was manually deleted.

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