Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-16827] [Branch-2.0] Avoid reporting spill metrics as shuffle metrics #15455

Closed
wants to merge 1 commit into from

Conversation

bchocho
Copy link
Contributor

@bchocho bchocho commented Oct 12, 2016

What changes were proposed in this pull request?

Fix a bug where spill metrics were being reported as shuffle metrics. Eventually these spill metrics should be reported (SPARK-3577), but separate from shuffle metrics. The fix itself basically reverts the line to what it was in 1.6.

How was this patch tested?

Cherry-picked from master (#15347)

@SparkQA
Copy link

SparkQA commented Oct 13, 2016

Test build #3336 has finished for PR 15455 at commit a53c64c.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@rxin
Copy link
Contributor

rxin commented Oct 13, 2016

Merging in. Thanks.

Can you also close the pr? GitHub wont' close it automatically because it is not merged into master branch.

asfgit pushed a commit that referenced this pull request Oct 13, 2016
…trics

## What changes were proposed in this pull request?

Fix a bug where spill metrics were being reported as shuffle metrics. Eventually these spill metrics should be reported (SPARK-3577), but separate from shuffle metrics. The fix itself basically reverts the line to what it was in 1.6.

## How was this patch tested?

Cherry-picked from master (#15347)

Author: Brian Cho <bcho@fb.com>

Closes #15455 from dafrista/shuffle-metrics-2.0.
@bchocho bchocho closed this Oct 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants