This repository was archived by the owner on Oct 23, 2024. It is now read-only.
Spark Dispatcher support for launching applications in the same virtual network by default #80
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Reference PR#45
What changes were proposed in this pull request?
This PR move Dispatcher default properties processing logic to an earlier phase when
MesosDriverDecriptionis being constructed. This change is needed for applying default properties (spark.mesos.network.*in this case) not only to Spark ExecutorsContainerInfobut to Spark Driver itself when it is launched on Mesos.How was this patch tested?