Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

crosscluster/logical: ldr replication lag metric not reported correctly during upgrade. #130078

Open
shailendra-patel opened this issue Sep 4, 2024 · 2 comments
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

Comments

@shailendra-patel
Copy link
Contributor

shailendra-patel commented Sep 4, 2024

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

@shailendra-patel shailendra-patel added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. A-disaster-recovery T-disaster-recovery 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 labels Sep 4, 2024
Copy link

blathers-crl bot commented Sep 4, 2024

Hi @shailendra-patel, please add branch-* labels to identify which branch(es) this C-bug affects.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

Copy link

blathers-crl bot commented Sep 4, 2024

cc @cockroachdb/disaster-recovery

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant