[KYUUBI-105]add a failover mode for kyuubi ha #106
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.
Is your feature request related to a problem? Please describe.
Kyuubi now supports load balance service mode for client to discover from a zookeeper namespace. In this mode, all kyuubi service instance uri in the namespace is randomly picked by the client itself.
The picked server will create a Spark application for this user(client). When this user create another client through zookeeper service discovery, there will be two very different situations. one is that the previous server is picked and the Spark application reused, the other one is that the previous server is not picked with a high probability and another Spark application will be created. This is good for large cluster which has enough resources. But for those cluster that are not well resourced, it is a waste to do so. When there're not enough resources to create a Spark application, the client will fail to create a session, which in fact should not happen.
Describe the solution you'd like
An Active/Standby mode may be able to overcome such a problem and still supply Kyuubi with high availability functions.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.