-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-05-08
-
0
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.
- is related to
-
SERVER-28988 add ReplicationProcess and use it to cache Rollback ID
- Closed
- related to
-
SERVER-45178 Rollback via refetch can cause rollback to happen successfully w/o updating the rollback id.
- Closed
-
SERVER-32776 Refresh rollback id cache on increment
- Closed