Skip to content

Conversation

@jsoltren
Copy link

This patch resurrects #7753 by liyezhang556520 and #17625 by jsoltren.

What changes were proposed in this pull request?

Memory reporting is a much desired feature in Apache Spark. This change adds reporting for some memory used by netty. We introduce a new executorMetrics object to track this.

This is a backend only change. No UI is included with this change.

How was this patch tested?

Ran https://github.com/jsoltren/spark-demos/blob/master/src/main/scala/org/soltren/spark/examples/ShuffleGroupCount.scala

@squito
Copy link
Contributor

squito commented Apr 25, 2017

Jenkins, ok to test

@SparkQA
Copy link

SparkQA commented Apr 25, 2017

Test build #76148 has finished for PR 17762 at commit 550c2d8.

  • This patch fails PySpark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@squito
Copy link
Contributor

squito commented Apr 26, 2017

Jenkins, retest this please

@SparkQA
Copy link

SparkQA commented Apr 26, 2017

Test build #76197 has finished for PR 17762 at commit 550c2d8.

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

@jsoltren
Copy link
Author

To close the loop here: I'm going to rework these ideas into a new JIRA that I'll file, to track total memory usage in the UI.

@jsoltren jsoltren closed this May 23, 2017
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