-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v4.2, v4.0, v3.6
-
Steps To Reproduce:
-
Sprint:Repl 2020-02-10, Repl 2020-02-24
-
Case:
-
Linked BF Score: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
-
- is documented by
-
DOCS-13417 Investigate changes in SERVER-45610: Some reads work while system is RECOVERING
-
- 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
-