[SERVER-30076] Use the UUID of the config.transactions collection for rollback via refetch Created: 10/Jul/17 Updated: 30/Oct/23 Resolved: 17/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| 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-31, Sharding 2017-08-21 |
| Participants: |
| Description |
|
The rollback by refetch algorithm will be changed to use collection UUIDs instead of collection names, so there needs to be a way to get the UUID of the config.transaction collection during rollback so its documents can be refetched. After the creation of the config.transaction collection (which is replicated), the generated UUID should be stored, and a method should be added to fetch it. |
| Comments |
| Comment by Githook User [ 17/Aug/17 ] |
|
Author: {'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}Message: |