Improve ZooKeeper client handling in migration code #10045
Merged
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.
Type of change
Description
The ZooKeeper client used to delete the
/controller
node during migration rollback is not closed properly when it fails. As a result, it might consumer resources or trying to connect long after its certificates might be deleted. This might cause issues if this happens in production. But it is also producing a large amounts of errors like this:in the unit tests where it seems to be able to easily produce hundreds of them while running the
cluster-operator
module unit tests. This PR uses the try-with-resource construct to make sure the client is closed.Checklist