crosscluster/logical: ldr replication lag metric not reported correctly during upgrade. #130078
Labels
A-disaster-recovery
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-testcluster
Issues found or occurred on a test cluster, i.e. a long-running internal cluster
P-2
Issues/test failures with a fix SLA of 3 months
T-disaster-recovery
During time of crdb upgrade from
24.2
->24.3
,Replication Lag
metric reported high value around ~15 hr for the duration of upgrade. This issue aims to look into LDR related metric weirdness.More details can be found in slack thread https://cockroachlabs.slack.com/archives/C2C5FKPPB/p1725436730058589
Jira issue: CRDB-41867
The text was updated successfully, but these errors were encountered: