-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Revert "Parallelize creating cluster snapshot" #7695
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: x13n The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
} | ||
|
||
// Maybe consider deleting from the list in the future. Maybe not. | ||
data.clearCaches() |
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.
Is revert the best option? Looks like this data.clearCaches()
is redundant when setting cluster state and its removal will fix the race.
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.
If you can quickly fix it then we can skip the revert I think
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.
But in general it is safer to revert first, and submit fixed version later, so that tests are not broken at HEAD.
/hold (#7695 (comment)) |
/lgtm |
Fixed in #7696, closing this one. |
Reverts #7630
There's a race condition when clearing the cache, which sometimes breaks unit tests: