-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Repl 2026-04-27, Repl 2026-05-11
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently in _isEligibleSyncSource, all nodes log the reason why a node they scan is not a valid sync source. Arbiters also go through this function, despite not maintaining a sync source, which leads to unnecessary and potentially misleading logs on the arbiter nodes. We should check if the node is an arbiter and not print any of these logs in that case.
Impact: We received direct requests from customers who experienced a pain point with this (SERVER-122481), and this is among many other HELP tickets regarding these logs being too frequent and causing issues with customer's log storage and ingestion.
- is depended on by
-
SERVER-122481 Frequent REPL logs: "Cannot select sync source because it is not readable" due to arbiter considered as sync source candidate
-
- Blocked
-
- related to
-
-
- Blocked
-
-
-
- Backlog
-