-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Server Programmability
-
ALL
-
-
Service Arch 2023-07-24, Service Arch 2023-08-07, Service Arch 2023-08-21, Service Arch 2023-09-04
Currently, recovering nodes with a non-zero priority are considered electable (see here and here). This implies that nodes that are neither secondary nor primary will show up in the hosts section of hello responses.
Mirrored reads rely on the members in the hosts section to choose mirroring targets (here), and due to the aforementioned issue, it may mirror reads to non-secondary nodes (see SERVER-60553). As part of this ticket, we should decide if:
- Recovering nodes should not be considered electable and this is an issue with the implementation of hello command that we need to fix.
- This is an issue with mirrored reads and we need to change the underlying mechanism that selects mirroring targets (e.g., using RSM).
Starting with the replication team to evaluate the first option. If this is not an issue with the implementation of hello, feel free to reassign to ServiceArch.
- related to
-
SERVER-60553 Secondary replicaset initial sync errors with "NotWritablePrimary: Not-primary error while processing 'find' operation on 'database_production' database via fire-and-forget command execution."
- Closed
-
SERVER-79329 Exclude lagged secondaries when selecting hosts for mirrored reads
- Backlog