[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: |
| Comment by Githook User [ 27/Jul/16 ] |
|
Author: {u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}Message: |
| 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. |