Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.1, 4.7.0, 4.2.16
Affects Version/s: 4.0.12
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.4, v4.2, v4.0, v3.6
Sprint:
Repl 2020-05-18
Case:
Linked BF Score:
6
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

(1 related to)

Assignee:: Samyukta Lanka
Reporter:: Siyuan Zhou
Participants:: Evin Roesle, Githook User, Judah Schvimer, Kelsey Schubert, Samyukta Lanka, Siyuan Zhou, Tess Avitabile
Votes:: 0 Vote for this issue
Watchers:: 12 Start watching this issue

Created:: Feb 15 2019 08:57:53 PM UTC
Updated:: Oct 29 2023 10:23:57 PM UTC
Resolved:: May 08 2020 07:48:35 PM UTC
Confidence Status Last Update:: 07/May/20 1:35 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates