Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.7.1
-
None
Description
From gopalv -
Trying to collect a hanging Tez AM logs, by killing the container and running yarn logs -applicationId application_1437098194051_0178 -am ALL
The output contains only one log file, which does not contain any of the actual execution logs, only the initialization logs.
From
YARN-3347, I note that// if we do not specify the value for CONTAINER_LOG_FILES option,
// we will only output syslogThis means that the person calling the yarn logs command has to list it out like this, to collect logs
yarn logs -applicationId application_1437098194051_0178 -am ALL -logFiles \
syslog_dag_1437098194051_0178_2_post,\
dag_1437098194051_0178_2-tez-dag.pb.txt,\
syslog_dag_1437098194051_0178_2,\
syslog_dag_1437098194051_0178_1_post,\
syslog_dag_1437098194051_0178_1,\
syslog,\
stdout,\
stderr,\
dag_1437098194051_0178_2.dot,\
dag_1437098194051_0178_1.dot,\
dag_1437098194051_0178_1-tez-dag.pb.txt
Attachments
Attachments
Issue Links
- is related to
-
YARN-4709 NMWebServices produces incorrect JSON for containers
- Resolved