-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Backport: "HBASE-29448: Modern backup failures can cause backup system to lock up" #7317
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
base: branch-2
Are you sure you want to change the base?
Conversation
32103e7
to
fa21ea2
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
5c6bcd3
to
8187004
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
8187004
to
4ddbf5d
Compare
4ddbf5d
to
6d32ea7
Compare
listSnapshots().stream().filter(s -> s.getName().equals(snapshotName)).findFirst() | ||
.orElseThrow(() -> new IOException("Snapshot " + snapshotName + " not found")); | ||
TableName tn = snapshot.getTableName(); | ||
disableTable(tn); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the same behavior as the logic we had in the BackupSystemTable that we're replacing. Does it makse sense to include this behavior? Or should this method do nothing by default?
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
No description provided.