[YARN-4149] yarn logs -am should provide an option to fetch all the log files

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.1
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: client, nodemanager
• Assignee: Varun Vasudev
• Reporter: Varun Vasudev
• Created: 11/Sep/15 17:01
• Updated: 30/Aug/16 01:16
• Resolved: 15/Sep/15 21:38

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 syslog

This 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

Issue Links

• is related to: YARN-4709 NMWebServices produces incorrect JSON for containers