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 "Prabhu Joseph (JIRA)" <ji...@apache.org> on 2019/05/29 18:01:00 UTC
[jira] [Comment Edited] (YARN-9542) Fix LogsCLI guessAppOwner
ignores custom file format suffix
[ https://issues.apache.org/jira/browse/YARN-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851117#comment-16851117 ]
Prabhu Joseph edited comment on YARN-9542 at 5/29/19 6:00 PM:
--------------------------------------------------------------
[~eyang] Can you review this Jira when you get time. This fixes YARN-9558 issue in branch-3.2 and 3.1 where older app log structure is present (without YARN-6929).
Failed testcase TestContainerManager is not related and it fails consistently in branch-3.2.
was (Author: prabhu joseph):
[~eyang] Can you review this Jira when you get time. This fixes YARN-9558 issue in branch-3.2 and 3.1 where older app log structure is present (without YARN-6929).
> Fix LogsCLI guessAppOwner ignores custom file format suffix
> -----------------------------------------------------------
>
> Key: YARN-9542
> URL: https://issues.apache.org/jira/browse/YARN-9542
> Project: Hadoop YARN
> Issue Type: Bug
> Components: log-aggregation
> Affects Versions: 3.2.0, 3.1.2
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Minor
> Attachments: YARN-9542-001.patch, YARN-9542-branch-3.2.001.patch, YARN-9542-branch-3.2.002.patch
>
>
> LogsCLI guessAppOwner ignores custom file format suffix yarn.log-aggregation.%s.remote-app-log-dir-suffix / Default IndexedFileController Suffix ({yarn.nodemanager.remote-app-log-dir-suffix}-ifile or logs-ifile). It considers only yarn.nodemanager.remote-app-log-dir-suffix or default logs.
> *Repro:*
> {code}
> yarn-site.xml
> yarn.log-aggregation.file-formats ifile
> yarn.log-aggregation.file-controller.ifile.class org.apache.hadoop.yarn.logaggregation.filecontroller.ifile.LogAggregationIndexedFileController
> yarn.log-aggregation.ifile.remote-app-log-dir app-logs
> yarn.resourcemanager.connect.max-wait.ms 1000
> core-site.xml:
> ipc.client.connect.max.retries 3
> ipc.client.connect.retry.interval 10
> Run a Job with above configs and Stop the RM.
> [ambari-qa@yarn-ats-1 ~]$ yarn logs -applicationId application_1557482389195_0001
> 2019-05-10 10:03:58,215 INFO client.RMProxy: Connecting to ResourceManager at yarn-ats-1/172.26.81.91:8050
> Unable to get ApplicationState. Attempting to fetch logs directly from the filesystem.
> Can not find the appOwner. Please specify the correct appOwner
> Could not locate application logs for application_1557482389195_0001
> [ambari-qa@yarn-ats-1 ~]$ hadoop fs -ls /app-logs/ambari-qa/logs-ifile/application_1557482389195_0001
> Found 1 items
> -rw-r----- 3 ambari-qa supergroup 18058 2019-05-10 10:01 /app-logs/ambari-qa/logs-ifile/application_1557482389195_0001/yarn-ats-1_45454
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org