[ 
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-13.1.txt

Tx for the review [~xgong]!
bq.  think that we could add the logic here. So, we do not need to do it 
separately inside several different functions.
This makes perfect sense - code reuse, yay!

Updating patch with the comments addressed.


> 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, YARN-5363-2016-07-13.1.txt, 
> YARN-5363-2016-07-13.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to