-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Repl 2024-06-10, Repl 2024-06-24, Repl 2024-07-08, Repl 2024-07-22, Repl 2024-08-05
Investigate if this can happen in production: someone does a backup to some data and then tries to do a PIT restore to immediately after, so that the config server (or any server) has no new writes in a sharded cluster.
If this is possible, it would hit fassert(8290701, reader.hasNext()).