[jira] [Created] (SPARK-23155) YARN-aggregated executor/driver logs appear unavailable when NM is down

["Gera Shegalov (JIRA)" <ji...@apache.org>]

Gera Shegalov created SPARK-23155:
-------------------------------------

             Summary: YARN-aggregated executor/driver logs appear unavailable when NM is down
                 Key: SPARK-23155
                 URL: https://issues.apache.org/jira/browse/SPARK-23155
             Project: Spark
          Issue Type: Improvement
          Components: Deploy
    Affects Versions: 2.2.1
            Reporter: Gera Shegalov


Unlike MapReduce JobHistory Server, Spark history server isn't rewriting container log URL's to point to the aggregated yarn.log.server.url location and relies on the NodeManager webUI to trigger a redirect. This fails when the NM is down. Note that NM may be down permanently after decommissioning in traditional environments or when used in a cloud environment such as AWS EMR where either worker nodes are taken away with autoscale, the whole cluster is used to run a single job.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org