-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
c2c: write unit test that ensures all jobs resume gracefully post cutover #107089
Labels
Comments
cc @cockroachdb/disaster-recovery |
msbutler
added a commit
to msbutler/cockroach
that referenced
this issue
Oct 13, 2023
msbutler
added a commit
to msbutler/cockroach
that referenced
this issue
Oct 16, 2023
msbutler
added a commit
to msbutler/cockroach
that referenced
this issue
Oct 16, 2023
msbutler
added a commit
to msbutler/cockroach
that referenced
this issue
Oct 16, 2023
msbutler
added a commit
to msbutler/cockroach
that referenced
this issue
Oct 26, 2023
craig bot
pushed a commit
that referenced
this issue
Oct 26, 2023
112357: streamingccl: test that replicated backup fails post cutover r=stevendanna a=msbutler Informs #107089 Epic: none Co-authored-by: Michael Butler <[email protected]>
closing as outdated. backup jobs on a new cluster should fail, and scheduled backups should pause. Changefeeds on the new cluster will fail Restore behavior is tracked here https://cockroachlabs.atlassian.net/browse/CRDB-30238 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
As far as I can tell, our unit tests currently only fingerpint and run a few select queries on the newly active tenant, post cutover. We should ensure Backup/Changefeed/Import jobs can resume gracefully, post cutover.
Jira issue: CRDB-29887
Epic CRDB-26968
The text was updated successfully, but these errors were encountered: