add variables with defaults to AWS EMR module#81
Open
Ken-Michalak wants to merge 2 commits intosegmentio:masterfrom
Open
add variables with defaults to AWS EMR module#81Ken-Michalak wants to merge 2 commits intosegmentio:masterfrom
Ken-Michalak wants to merge 2 commits intosegmentio:masterfrom
Conversation
Without ssh access, there's no way to clean up Spark's job history, and the cleaner is disabled by default. This enables the cleaner with the default values and allows modifications. https://repost.aws/knowledge-center/core-node-emr-cluster-disk-space https://spark.apache.org/docs/latest/monitoring.html#spark-history-server-configuration-options
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This allows for some additional configuration, but defaults to the current hard-coded or empty values. The important one for us is the
key_nameso that we can do some troubleshooting.Adding
unhealthy_node_replacementwould be a breaking change for v4 that the example uses, so I just commented that out until it's been updated.