-
Notifications
You must be signed in to change notification settings - Fork 18
[manager] delete fail when CAS/CAD fail #68
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
The retry loop here changes the semantics of delete failures in a couple of important ways that may cause issues in production.
When
DoLocationDelTasksetsresult.statusto a non-OK value because of storage delete failures (e.g.,Deletereturning errors) or early error paths likeHandleErrorPromisein the executor,fail_metascan still be empty. In that case this branch builds aCacheLocationDelRequestwhoseblock_keysandlocation_idsare both empty. TheSchedulePlanExecutor::Submit(const CacheLocationDelRequest&)overload treats an empty task as success and immediately sets aPlanExecuteResult{EC_OK, "", {}}. As a result, a real failure in the original delete operation is effectively converted into an apparent success on the retry, and the supervisor logs the task as finished successfully. This hides the original error from operators and makes it hard to understand why deletes sometimes fail.For true CAD partial failures where
fail_metasis populated, this loop will keep resubmitting delete requests as long asdel_result.status != EC_OKandSubmitcontinues to return a valid future. There is no retry limit, no backoff, and no distinction between transient and permanent failure codes. If a backend consistently returns non-OK status for those locations, this cell can be requeued indefinitely with zero delay, continually issuing requests and warnings and potentially starving the queue.Would it make sense to (a) only build a retry request when
fail_metasis non-empty, and (b) introduce some explicit retry policy (max attempts or backoff, and possibly short-circuit on clearly permanent error codes) so we don’t turn persistent CAD errors into an unbounded tight loop?🤖 Generated by Qoder • Fix in Qoder