GitHub user markgrover opened a pull request:
https://github.com/apache/spark/pull/8093
SPARK-9790: [YARN] Expose in WebUI if NodeManager is the reason why
executors were killed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markgrover/spark nm2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/8093.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #8093
----
commit f3cceb131a0d5a4fcbc8a6a072b7303dba0266b4
Author: Mark Grover <[email protected]>
Date: 2015-08-07T00:12:52Z
Testing some changes
commit a63f505dbd1aee14184a0857925d6d8a055bc94f
Author: Mark Grover <[email protected]>
Date: 2015-08-07T00:58:59Z
Mixing things up a bit
commit d2a9295cbebde00c4b4158373fda977ee3d59cf6
Author: Mark Grover <[email protected]>
Date: 2015-08-07T16:09:58Z
Fixing a bug in the name of the message.
Also, adding a redirect in Yarn backed to simply use the CoarseGrained's
function
commit db9e250de38fe345399efa6022cb2d075cf3a68e
Author: Mark Grover <[email protected]>
Date: 2015-08-07T17:06:55Z
My code is YARN specific so make it so
commit 6d8460225a5f87d5443fcc18ae757086c1398a8f
Author: Mark Grover <[email protected]>
Date: 2015-08-08T15:25:45Z
Updating definitions to send reason. Now we have to use it somewhere
commit 295600432c5e93bf45044084a87ce6c85b6e2eec
Author: Mark Grover <[email protected]>
Date: 2015-08-08T15:28:05Z
Added usage for reason
commit 14b033ca1f941ecf95fe47d86e4bdd95a24dbd42
Author: Mark Grover <[email protected]>
Date: 2015-08-09T15:28:07Z
1. Adding reason to ExecutorLoss message
2. But also and more importantly, adding to the existing RemoveExecutor
message so may be we don't need a whole new message
commit 49f5e22aeb03b809f413eca0b928b29c95cdefaa
Author: Mark Grover <[email protected]>
Date: 2015-08-09T16:42:27Z
Trying to get rid of the ContainerExited message since it may be possible
to achieve that via overloading the RemoveExecutor message
commit 79bb8dd487adbb2a28c12e909eba56db743ae12d
Author: Mark Grover <[email protected]>
Date: 2015-08-10T04:32:45Z
Revert "Trying to get rid of the ContainerExited message since it may be
possible to achieve that via overloading the RemoveExecutor message"
This reverts commit db2b4b25fbf004e935fa7455979395c2b73506b4.
commit 9bb434fa9fe5d1cd34d4b17fcefe8afad43aea9f
Author: Mark Grover <[email protected]>
Date: 2015-08-10T04:35:08Z
Preserving some good changes from the reverted commit
commit 0f9d6f557d7682974484a2eceb021472b16178fd
Author: Mark Grover <[email protected]>
Date: 2015-08-10T21:04:13Z
Fixing scalastyle. Updating some tests
commit 4576eda97b25b4779848cb5ac60e85e809f14103
Author: Mark Grover <[email protected]>
Date: 2015-08-11T03:13:46Z
Added some logging
commit 47c20c0f794d654bc4c7f08809373274cc16b7be
Author: Mark Grover <[email protected]>
Date: 2015-08-11T04:37:28Z
Getting rid of the extra ContainerRemoved message since it doesn't seem
like it's neccessary
commit 4a4109fe0318b9403a68a60df5b44a0cc0f00f76
Author: Mark Grover <[email protected]>
Date: 2015-08-11T04:43:06Z
Updating the displayed error message
commit 67b9f20eba05941ed37a33305dcdc8210a1e5c41
Author: Mark Grover <[email protected]>
Date: 2015-08-11T04:46:50Z
Minor updates
----
---
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]
