[
https://issues.apache.org/jira/browse/TEZ-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14114393#comment-14114393
]
Hitesh Shah commented on TEZ-1495:
----------------------------------
Overall comments:
- please look at TimelineClientImpl in yarn code for supporting secure
clusters
- At this point, it looks like there is no timeline client dependency so
this should be ok to be in tez-api.
- Regarding the current switch between AM and ATS, I think it should
probably be a one-time switch. Once the client switches over to ATS, it should
stick to ATS. This implies knowing when the final switchover needs to happen
i.e on AM completion or when the session switches to a different DAG. You may
wish to look at TestOrderedWordCount and modify it to test whether DAGClient
for the client for the first dag works as intended while the second dag is
running.
Regarding
{code}
+ // Status of the DAG is updated only when it completes. default to RUNNING
if no status found
+ // as the ATS is not updated until the status of dag is running.
{code}
- maybe the DAG status should be updated to running whenever the dag started
event is logged?
> ATS integration for TezClient
> -----------------------------
>
> Key: TEZ-1495
> URL: https://issues.apache.org/jira/browse/TEZ-1495
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Prakash Ramachandran
> Assignee: Prakash Ramachandran
> Attachments: TEZ-1495.1.patch, TEZ-1495.2.patch, TEZ-1495.WIP.1.patch
>
>
> Tez client should automatically redirect to ATS when the AM is not running.
> All APIs exposed ( DAG status, counters, etc ) from the DAGClient should
> continue to work after the AM has shut down.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
