-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.0.12
-
Component/s: Replication
-
None
-
Fully Compatible
-
v4.4, v4.2, v4.0, v3.6
-
Repl 2020-05-18
-
(copied to CRM)
-
6
Since we no longer kill readers and close their connections on stepdown, the nodes syncing from the primary may not have a chance to choose a new sync source even if chaining is disabled.
SERVER-21537 has similar symptoms when the heartbeats are stale. Both of them can be addressed in the Smart Chaining project.
- is duplicated by
-
SERVER-21537 chainingAllowed = false not being enforced after rs.stepDown()
- Closed
-
SERVER-43615 syncSource diagnostics are incorrect
- Closed
- is related to
-
SERVER-49708 Election with chaining disabled doesn't make node change sync source
- Closed
-
SERVER-74425 Can not Select Primary when chaining allowed option disabled.
- Closed
-
SERVER-58412 Changing settings.chainingEnabled in replica set configuration should affect change in sync sources
- Closed
- related to
-
SERVER-44603 Consider having tailable readPreference "primary" queries killed on stepdown
- Backlog