Don't set the mapred.job.tracker config option #27
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.
Configuring this option causes issues with track tracker connectivity when using the HA JobTracker configuration mode. I assume the reason this option is set is due to the fact hadoop doesn't require you configure this option on the actual JobTracker, only the clients (and task trackers)?
This probably isn't the right fix, however I wanted to open up discussion. Perhaps we could only set the option if it's not currently configured on the config object?
Would appreciate any thoughts, @brndnmtthws?