-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.2, v4.0, v3.6
-
-
Repl 2020-02-10, Repl 2020-02-24
-
(copied to CRM)
-
32
While the replication system is in RECOVERING, we cannot read collection data (error code NotMasterOrSecondary). However, provided we have allowed secondary reads, we CAN do a listDatabases or listCollections or listIndexes. This seems bad, since the results of these reads may represent database states which are inconsistent or at a point in time prior to a previously reported lastDurable time of the node.
- duplicates
-
SERVER-39596 While a node is not in primary/secondary state, dbStats/collStats should not hang
- Closed
- related to
-
SERVER-46190 Disallow 'dbHash' for nodes in RECOVERING state
- Closed
-
SERVER-48379 ReplSetTest should wait for secondaries before checking db hashes
- Closed