[SERVER-27659] persist Rollback ID and read it at startup Created: 12/Jan/17 Updated: 16/Dec/19 Resolved: 29/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Repl 2017-05-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
Currently we randomize rollback IDs at startup to reduce the chance of collisions. This does not prevent collisions entirely and makes it so rollback IDs that are randomly chosen very close to MaxInt could rollover into the negatives which is somewhat undefined behavior. We should simply persist the rollback ID (waiting for it to be durable) and read it at startup like lastVote to avoid these issues. |
| Comments |
| Comment by Githook User [ 03/May/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 29/Apr/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |
| Comment by Githook User [ 28/Apr/17 ] |
|
Author: {u'username': u'adamlsd', u'name': u'ADAM David Alan Martin', u'email': u'adam.martin@10gen.com'}Message: Revert " This reverts commit ac6f185017f76cc7124373e97a2c55291d5c8956. |
| Comment by Githook User [ 21/Apr/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |