[
https://issues.apache.org/jira/browse/TEZ-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117058#comment-14117058
]
Siddharth Seth commented on TEZ-1476:
-------------------------------------
[~zjffdu] - there's two APIs on DAGClient which can be used for monitoring.
waitForCompletion does not print vertex status updates, if that's what you're
looking for.
Please open jiras for the issues you mentioned. I'm +1 for adding indentation
to the VertexOutput. In terms of printing Vertex information - StatusGetOpts
could be used.
> DAGClient waitForCompletion output is confusing
> -----------------------------------------------
>
> Key: TEZ-1476
> URL: https://issues.apache.org/jira/browse/TEZ-1476
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Siddharth Seth
> Assignee: Jonathan Eagles
> Priority: Critical
> Fix For: 0.5.0
>
> Attachments: TEZ-1476-v1.patch, TEZ-1476-v2.patch
>
>
> When a DAG is submitted - "2014-08-21 16:38:06,153 INFO [main]
> rpc.DAGClientRPCImpl (DAGClientRPCImpl.java:log(428)) - Waiting for DAG to
> start running" is logged.
> After this, nothing seems to get logged till the first task completes.
> It would be useful to log when the state changes to RUNNING - as well as at
> least one line stating the number of tasks, etc (0% progress line). Also,
> progress could be logged every few seconds irrespective of whether it has
> changed or not to give the impression that the job has not just gotten stuck.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
