[
https://issues.apache.org/jira/browse/TEZ-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931231#comment-13931231
]
Hitesh Shah commented on TEZ-700:
---------------------------------
bq. DAG progress could be an option? That means, we can keep the last progress
count and check if there is any progress made since last write. However, that
would create an issue if something got stuck, no progress changes and nothing
would be printed.
Is nothing being printed an issue? Consider a case where someone is just
watching the console and seeing the DAG remain at x% for an indefinite amount
of time - what would be a good user experience?
With respect to tracking changes, I believe either the DAG progress alone (
along with any state changes ) or a combination of both DAG and vertex data
could be easily used to track if something has changed.
> Helper API's to monitor a DAG to completion
> -------------------------------------------
>
> Key: TEZ-700
> URL: https://issues.apache.org/jira/browse/TEZ-700
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Mohammad Kamrul Islam
> Attachments: TEZ-700.1.patch, TEZ-700.2.patch, TEZ-700.3.patch
>
>
> There is a lot of boiler plate code to monitor a dag progress to completion.
> A simple API to monitor the job to completion will be reduce this burden.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
