-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.6.2
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2018-02-12, Repl 2018-02-26
We currently empty the cache on increment and then refresh it when we call getRollbackID next. This means that server status calls can go to disk when the cache needs to be refreshed. Incrementing the rollback id happens during rollback (which is slow and rare) so it does not matter if we go to storage one more time. We should also refresh the cache on startup for the same reason.
- is related to
-
SERVER-28988 add ReplicationProcess and use it to cache Rollback ID
- Closed
-
SERVER-31662 Initialize rbid to 1 and log when it changes
- Closed
-
SERVER-15820 Include rollback ID in 'repl' section of serverStatus
- Closed
-
SERVER-27659 persist Rollback ID and read it at startup
- Closed