[WIP][SPARK-29564][SQL] Cluster deploy mode should support Spark Thrift server #26223
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LantaoJin
changed the title
|
Test build #112525 has finished for PR 26223 at commit
|
|
How do you get thrift ip/port in cluster mode? |
|
I mark this to WIP since it needs more code to implement this feature. I will update a design doc in Jira soon. |
|
Hi, @LantaoJin . |
|
thanks @dongjoon-hyun , I am busy with re-developing delta-lake in corp inner. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this pull request?
Cluster deploy mode is not applicable to Spark Thrift server now. This restriction is too rude.
In our production, we use multiple Spark Thrift servers as long running services which are used yarn-cluster mode to launch. The life cycle of STS is managed by upper layer manager system which is also used to dispatcher user's JDBC connection to applicable STS.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manually test with command: