-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
-
Repl 2025-08-18, Repl 2025-09-01, Repl 2025-09-15, Repl 2025-09-29, Repl 2025-10-13, Repl 2025-10-27, Repl 2025-11-24, Repl 2026-02-16
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In WRITING-35824 we reviewed blocking heartbeats for nodes in stepdown to prevent a mismatch between the ReplSetConfig and topology coordinator's term. It's unclear if this inconsistency currently results in any bugs. We need to investigate two things:
1. is it possible for this inconsistency to cause undesirable conditions like a node incorrectly thinking it's a primary or race conditions?
2. Is it possible to refactor the code so that these are always consistent?
- is related to
-
SERVER-107412 Make sure a stepping down node updates its term before it accepts a reconfig with that term
-
- Closed
-