[KYUUBI #6052] Support to delete EngineSpace ZNodes in all share levels #6086
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.
🔍 Description
Issue References 🔗
This pull request implements #6052
Describe Your Solution 🔧
This PR introduced a new config
kyuubi.ha.engine.cleanup.enabled
.If
kyuubi.ha.engine.cleanup.enabled
is set to true, Engine will delete namespace node and lock node on ZooKeeper when stops.This feature can be used to cleanup ZooKeeper nodes created by Engine with random subdomains.
Note: User should guarantee Engine with same namespace won't be launched before old Engine stops. Otherwise, errors may happen when launching new Engine.
Types of changes 🔖
Test Plan 🧪
Behavior Without This Pull Request ⚰️
Engine namespace node and lock node remain when Engine stops.
Behavior With This Pull Request 🎉
If
kyuubi.ha.engine.cleanup.enabled
is set to true, Engine will delete namespace node and lock node when stops.Related Unit Tests
Kyuubi #6052: Cleanup engine namespace node and lock node
Checklist 📝
Be nice. Be informative.