-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Security
-
Repl 2021-10-18, Repl 2021-11-01, Replication 2021-11-15, Replication 2021-11-29, Replication 2021-12-13, Replication 2021-12-27, Replication 2022-01-10, Replication 2022-01-24, Replication 2022-02-07, Repl 2022-02-21, Repl 2022-03-07, Repl 2022-03-21, Repl 2022-04-04, Repl 2022-04-18, Repl 2022-05-02, Repl 2022-05-16, Repl 2022-05-30, Repl 2022-06-13, Repl 2022-06-27, Repl 2022-07-11, Repl 2022-08-08, Repl 2022-08-22, Repl 2022-09-05, Repl 2022-09-19, Repl 2022-07-25, Repl 2022-10-03, Repl 2022-10-17, Repl 2022-10-31, Repl 2022-11-14, Repl 2022-11-28, Repl 2022-12-12, Repl 2022-12-26, Repl 2023-01-09, Repl 2023-01-23, Repl 2023-02-06, Repl 2023-02-20, Repl 2023-03-06, Repl 2023-03-20, Repl 2023-04-03, Repl 2023-04-17, Repl 2023-05-01, Repl 2023-05-15, Repl 2023-05-29, Repl 2023-06-12, Repl 2023-06-26, Repl 2023-07-10, Repl 2023-07-24, Repl 2023-08-07, Repl 2023-08-21
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Today, when a replica set member is in RECOVERING state, we do not allow reading data to signify drivers to redirect reads to other members.
It will be useful to allow internal reads like serverStatus to read data. This would allow us to have FTDC collected during the time a member is in RECOVERING state. One example is the compact command during which we move a secondary member into RECOVERING state and during all this time FTDC is not collected (and thus, difficult to diagnose).
- is related to
-
SERVER-58026 Omitted FTDC sections cause frequent schema changes that limit FTDC retention
-
- Backlog
-