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.

Sign up for GitHub

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

Jump to bottom

c2c: after cutover, verify that all in progress restore jobs continue running #107876

Closed
msbutler opened this issue Jul 31, 2023 · 3 comments
Closed

c2c: after cutover, verify that all in progress restore jobs continue running #107876

msbutler opened this issue Jul 31, 2023 · 3 comments
Assignees
@msbutler
Labels
A-disaster-recovery C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-disaster-recovery
Projects
Disaster Recovery Backlog

Comments

@msbutler
Copy link
Collaborator

msbutler commented Jul 31, 2023 •
edited

Once the application tenant comes online after cutover, all in-progress restore jobs should continue running, if the dba sees that the restore hogs resources, they can take action and cancel/pause the job.

Relates to umbrella issue #107089

Jira issue: CRDB-30238

Epic CRDB-26968
@msbutler msbutler added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-disaster-recovery labels Jul 31, 2023
@blathers-crl
Copy link

blathers-crl bot commented Jul 31, 2023

cc @cockroachdb/disaster-recovery

@msbutler msbutler changed the title c2c: after cutover, all in progress restore jobs should pause c2c: after cutover, verify that all in progress restore jobs should continue running Aug 2, 2023
@msbutler msbutler changed the title c2c: after cutover, verify that all in progress restore jobs should continue running c2c: after cutover, verify that all in progress restore jobs continue running Aug 2, 2023
@msbutler msbutler self-assigned this Aug 2, 2023
@msbutler msbutler mentioned this issue Aug 2, 2023
Closed
@stevendanna
Copy link
Collaborator

Closing this as we went a different direction: #111578

Disaster Recovery Backlog automation moved this from Triage to Done Feb 13, 2024
@msbutler
Copy link
Collaborator Author

@stevendanna I think we need to keep this one open and finish it up

@msbutler msbutler reopened this Feb 13, 2024
Disaster Recovery Backlog automation moved this from Done to Triage Feb 13, 2024
Disaster Recovery Backlog automation moved this from Triage to Done Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@msbutler msbutler

Labels
A-disaster-recovery C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-disaster-recovery
Projects
Disaster Recovery Backlog
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stevendanna @msbutler