Github user jdanbrown commented on the pull request:
https://github.com/apache/spark/pull/2744#issuecomment-62656350
@sryza I came across your PR while searching for ways to debug pyspark yarn
containers running over yarn memory limits. This change will be very helpful;
what are your thoughts on dumping the container process listing as well, like
yarn MR tasks do? That's killer for figuring out which process in your
container is out of control, like in the case of pyspark where you have a jvm
and python processes to deal with.
Example:
-
https://gist.githubusercontent.com/jdanbrown/cef65e9082b1f32d085e/raw/83347253348f246aa4f9989993e8fb6db14db313/gistfile1.txt
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
