HubSpot Backport: MAPREDUCE-6660 Add MR Counters for bytes-read-by-network-distance FileSystem metrics #51
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
bbeaudreault
force-pushed
the
backport-MAPREDUCE-6660
branch
3 times, most recently
from
9301b3d to
d227997
Compare
…twork-distance FileSystem metrics
bbeaudreault
force-pushed
the
backport-MAPREDUCE-6660
branch
from
d227997 to
6079ee6
Compare
bbeaudreault
force-pushed
the
backport-MAPREDUCE-6660
branch
from
b6bb9b1 to
b2c51ce
Compare
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.
The jira https://issues.apache.org/jira/browse/MAPREDUCE-6660 was never merged, but I think this will be useful for us in evaluating cross-AZ transfer costs. I think we should consider taking up MAPREDUCE-6660 to get it merged upstream. For now I want to see this in our env.
It probably will require us to configure our NM pods with topology.script.file.name (if not already) and fs.client.resolve.topology.enabled.