[
https://issues.apache.org/jira/browse/YARN-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402489#comment-15402489
]
Junping Du commented on YARN-5226:
----------------------------------
bq. We are using YarnClient which would handle all the cases, including the
check on whether the timeline service is enabled.
Actually, I am talking about LogsCLI#fetchAMContainerLogs() where we call
getAMContainerInfoForAHSWebService() internally. User cannot differentiate the
failure is due to ATS not enabling in server side or networking failures so I
think it could be better to have a check similar to what we have in YarnClient.
BTW, in long run, I think we could prefer to have a remote RPC call to get ATS
status (enabled/disabled) from RM instead of client side configuration check -
this is because the possible inconsistency between configurations from client
and server.
> remove AHS enable check from LogsCLI#fetchAMContainerLogs
> ---------------------------------------------------------
>
> Key: YARN-5226
> URL: https://issues.apache.org/jira/browse/YARN-5226
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Attachments: YARN-5226.1.patch, YARN-5226.2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
