-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In the rollback code, we log the rollback common point before performing a series of checks against the local replication state. If any of these checks fail, we would abort the rollback attempt and shut the server down with a fatal assertion (see SERVER-50071). It would be helpful for diagnosing some of these failed checks if we logged the relevant replication optimes along with the common point.
- is related to
-
SERVER-101829 Consider changing invariants while finding common point for rollback to be fasserts
-
- Closed
-
-
SERVER-50071 Change rollback common point checks in rollback_impl.cpp from invariants to fasserts
-
- Closed
-
- related to
-
SERVER-123285 revisit rollback common optime constraints
-
- Needs Scheduling
-