Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- former-quick-wins

Assigned Teams:

Replication
Confidence Status:
None
Work Order:
3

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

Right now we have multiple ideas of whether a node is up or down; one called _health and the other called stale. These affect each other in different ways depending on whether we are a primary, secondary, or arbiter. We should figure out what we really want and combine this in a clearer way.

is duplicated by

SERVER-29099 liveness timeout is only rescheduled on replSetUpdatePosition commands

Closed

is related to

SERVER-34728 Heartbeats are used to advance replication commit point

Closed

SERVER-30716 Log whenever a node updates its view of another node to consider it down

Backlog

related to

SERVER-31963 Remove code for replication protocol version 0

Closed

SERVER-29076 Replace all usage of heartbeat op times with lastAppliedOpTime / lastDurableOptime

Backlog

SERVER-29078 Eliminate use of memberHeartbeatData in replication_coordinator_impl

Closed

(1 related to)

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Matthew Russotto
Participants:: [DO NOT USE] Backlog - Replication Team, Matthew Russotto
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: May 04 2017 08:39:06 PM UTC
Updated:: Dec 06 2022 04:01:50 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates