cockroachdb / cockroachdb/cockroach
PCR replication lag post-failover
Open
24.1
A-disaster-recovery
branch-release-24.1
C-bug
P-1
T-disaster-recovery
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
After failover, we should set the PCR replication lag to 0. We do not do so today and therefore after failback the original standby cluster still emits a growing replication lag. see https://cockroachlabs.slack.com/archives/C2C5FKPPB/p1754402056390949 for more information.
Jira issue: CRDB-53337
Epic CRDB-50820
Contributor guide
Research direction
Start by tracing PCR replication-lag handling through the failover and failback paths, using the linked Jira issue CRDB-53337 and Slack discussion for context. Done means the lag is set to 0 after failover and the original standby cluster no longer emits a growing lag after failback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100