[ https://issues.apache.org/jira/browse/SPARK-9790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Grover updated SPARK-9790: ------------------------------- Attachment: error_showing_in_UI.png Attaching an image of what the error message in the UI would now look like. > [YARN] Expose in WebUI if NodeManager is the reason why executors were killed. > ------------------------------------------------------------------------------ > > Key: SPARK-9790 > URL: https://issues.apache.org/jira/browse/SPARK-9790 > Project: Spark > Issue Type: Bug > Components: YARN > Affects Versions: 1.4.1 > Reporter: Mark Grover > Attachments: error_showing_in_UI.png > > > When an executor is killed by yarn because it exceeds the memory overhead, > the only thing spark knows is that the executor is lost. The user has to go > track search through the NM logs to figure out that its been killed by yarn. > It would be much nicer if the spark-driver could be notified why the executor > was killed. Ideally it could both log an explanatory message, and update the > UI (and the eventLog) so that it was clear why the executor was lost. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org