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: in SHOW LDR JOBS, either report rounded down replicated time, or replicatedTimeEpoch #130114

Open
msbutler opened this issue Sep 4, 2024 · 2 comments
Labels
A-disaster-recovery C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-disaster-recovery

Comments

@msbutler
Copy link
Collaborator

msbutler commented Sep 4, 2024

To ensure resumption from a cursor without data loss, the user relies on the replicated time provided by SHOW LDR JOBS. The stringified replicated time may get rounded past the persisted hlc.timestamp to the nearest microsecond. Instead, we should intentionally round down the replicated time presented in SHOW LDR JOBS, or also post the replicatedTimeEpoch (AOST) as a decimal.

Jira issue: CRDB-41878

Epic CRDB-40869

@msbutler msbutler added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-disaster-recovery labels Sep 4, 2024
Copy link

blathers-crl bot commented Sep 4, 2024

cc @cockroachdb/disaster-recovery

@msbutler
Copy link
Collaborator Author

msbutler commented Oct 3, 2024

this still needs to be done.

@msbutler msbutler reopened this Oct 3, 2024
@msbutler msbutler removed their assignment Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-disaster-recovery C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-disaster-recovery
Projects
None yet
Development

No branches or pull requests

1 participant