-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 3.7.4
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
Repl 2018-04-09
-
21
The LogicalClock is not initialized when performing replication recovery at startup. Completing a background secondary[1] index must set a legal timestamp. However the predicate to assign a timestamp fails because `startup` is not guaranteed to have a valid logical clock state.
[1] It's perhaps unclear why I call the index build a background secondary index build. The index build is kicked off by an oplog entry and as such intersects much of the same code path as a typical secondary index build.
- is duplicated by
-
-
- Closed
-
- is related to
-
SERVER-43097 Improve log messaging when index builds get foregrounded because of startup recovery
-
- Closed
-
- related to
-
-
- Closed
-