[SERVER-29759] on _configsvrSetFeatureCompatibilityVersion=3.6, generate and persist UUIDs for existing sharded collections Created: 20/Jun/17 Updated: 30/Oct/23 Resolved: 26/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.8 |
| Fix Version/s: | 3.5.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-07-10 |
| Participants: |
| Description |
|
Make sure to only generate UUIDs for sharded collections that don't already have one, to make the _configsvrSetFeatureCompatibilityVersion idempotent. (Otherwise, we might change the UUID after it was already generated, and after some shards had already read the UUID value and set the UUID in their storage engines). |
| Comments |
| Comment by Githook User [ 26/Jun/17 ] |
|
Author: {u'username': u'EshaMaharishi', u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}Message: |