You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2016/07/12 21:34:20 UTC
[jira] [Updated] (YARN-5363) For AM containers, or for containers
of running-apps, "yarn logs" incorrectly only (tries to) shows syslog
file-type by default
[ https://issues.apache.org/jira/browse/YARN-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated YARN-5363:
------------------------------------------
Attachment: YARN-5363-2016-07-12.txt
Here's a straightforward patch - based on top of YARN-3200.
- Changes the default to be {{.*}} instead of {{syslog}} for all containers (including AM containers - YARN-3347.
- Also renamed the inaptly named {{logFiles}} option to be {{log_files}} - naming CLI options in camelCase is not the norm.
- Added a mock test - we are missing real tests for logs of running applications.
> For AM containers, or for containers of running-apps, "yarn logs" incorrectly only (tries to) shows syslog file-type by default
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-5363
> URL: https://issues.apache.org/jira/browse/YARN-5363
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: log-aggregation
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Attachments: YARN-5363-2016-07-12.txt
>
>
> For e.g, for a running application, the following happens:
> {code}
> # yarn logs -applicationId application_1467838922593_0001
> 16/07/06 22:07:05 INFO impl.TimelineClientImpl: Timeline service address: http://<TS-host-name>:8188/ws/v1/timeline/
> 16/07/06 22:07:06 INFO client.RMProxy: Connecting to ResourceManager at <RM-host-name>/<RM-IP>:8050
> 16/07/06 22:07:07 INFO impl.TimelineClientImpl: Timeline service address: http://<TS-host-name>l:8188/ws/v1/timeline/
> 16/07/06 22:07:07 INFO client.RMProxy: Connecting to ResourceManager at <RM-host-name>/<RM-IP>:8050
> Can not find any log file matching the pattern: [syslog] for the container: container_e03_1467838922593_0001_01_000001 within the application: application_1467838922593_0001
> Can not find any log file matching the pattern: [syslog] for the container: container_e03_1467838922593_0001_01_000002 within the application: application_1467838922593_0001
> Can not find any log file matching the pattern: [syslog] for the container: container_e03_1467838922593_0001_01_000003 within the application: application_1467838922593_0001
> Can not find any log file matching the pattern: [syslog] for the container: container_e03_1467838922593_0001_01_000004 within the application: application_1467838922593_0001
> Can not find any log file matching the pattern: [syslog] for the container: container_e03_1467838922593_0001_01_000005 within the application: application_1467838922593_0001
> Can not find any log file matching the pattern: [syslog] for the container: container_e03_1467838922593_0001_01_000006 within the application: application_1467838922593_0001
> Can not find any log file matching the pattern: [syslog] for the container: container_e03_1467838922593_0001_01_000007 within the application: application_1467838922593_0001
> Can not find the logs for the application: application_1467838922593_0001 with the appOwner: <app-owner>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org