-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
backupccl: stop blocking backup/restore jobs on client disconnect #51999
Conversation
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.
Reviewed 2 of 2 files at r1.
Reviewable status:complete! 0 of 0 LGTMs obtained
do we need to do RESTORE too? |
Yep, was going to follow up in a separate PR - but I may as well as bundle it with this one. Will push the changes here. |
Updated with RESTORE, RFAL. |
Previously, a backup job whose client disconnect might have blocked on sending its results to the resultCh (and thus block forever). This commit allows these jobs to complete. Release note (bug fix): Previously, a BACKUP job would block once it finished backing up the data.
This commit prevents RESTORE from blocking when sending its results back over resultCh if the client that started the job disconnects. Release note (bug fix): Previously, RESTORE would sometimes block at the end of the job when sending its results back if the connection that started the job disconnected. This is now fixed.
TFTR! |
Build succeeded: |
Previously, a backup/restore job whose client disconnect might have blocked on
sending its results to the resultCh (and thus block forever). This
commit allows these jobs to complete.
Release note (bug fix): Previously, a BACKUP/RESTORE jobs would
sometimes block once it finished executing the job. This is now fixed.