Setup request consumer for new cluster #1388
Merged
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
amCap1712
changed the title
mayhem
approved these changes
Apr 14, 2021
amCap1712
force-pushed
the
spark-new-cluster
branch
2 times, most recently
from
f4e1227
to
006d20f
Compare
amCap1712
force-pushed
the
spark-new-cluster
branch
from
006d20f
to
a1852b2
Compare
amCap1712
force-pushed
the
spark-new-cluster
branch
from
42adf40
to
4d86612
Compare
|
Dockerfile.spark.newcluster will be nenamed in a subsequent PR. |
|
This is the new setup we are currently using in production. The changes here are only one half of the story and not enough to reproduce the cluster on another set of machines. I hope to put up some document explaining the steps to setup a cluster soon. |
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.
Modify the request consumer setup to work with the new cluster setup. Since we have now installed spark on the host directly, we do not need to include it in the docker image.
We'll also need to change the configuration parameters according to the resources available on the host and yarn cluster manager.