[SERVER-29636] Add logic for falling back to no_uuid rollback algorithm Created: 14/Jun/17 Updated: 29/Jan/18 Resolved: 28/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | Backlog |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Chang | Assignee: | Allison Chang |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2017-06-19, Repl 2017-07-10 |
| Participants: |
| Description |
|
We want to add new logic into bgsync.cpp to fall back onto the no_uuid rollback algorithm if we are in featureCompatibilityVersion 3.4 instead of 3.6. This is needed because UUID's are a feature included in 3.6 and not 3.4. Thus, if the featureCompatibilityVersion of the cluster is not 3.6, we want to ensure that the no_uuid rollback algorithm is used to prevent compatibility issues. |
| Comments |
| Comment by Allison Chang [ 28/Jun/17 ] |
|
Completed in |