Skip to content

fix: insert replica when removed by cleanup #10917

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 3 commits into from
Nov 28, 2023
Merged

Conversation

f0ssel
Copy link
Contributor

@f0ssel f0ssel commented Nov 28, 2023

I didn't feel great about changing the database query because there's other things besides this loop that call it, and I don't feel those callers have the same authority about re-inserting on update. Let me know if that is not a correct assumption.

Closes #8858

This reverts commit 71076ee.
@f0ssel
Copy link
Contributor Author

f0ssel commented Nov 28, 2023

Upgrading the logs to error level created new flakes in the TwentyConcurrent tests. I timeboxed trying to find the issue but couldn't find a solution to the race. You can see the failed tests in CI for more info, I've reverted that commit and will merge the rest of the changes.

@f0ssel f0ssel merged commit afbda22 into main Nov 28, 2023
@f0ssel f0ssel deleted the f0ssel/replica-upsert-2 branch November 28, 2023 19:15
@github-actions github-actions bot locked and limited conversation to collaborators Nov 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

replicasync: deleting temporarily unhealthy replica breaks node even after it recovers
3 participants