[
https://issues.apache.org/jira/browse/TEZ-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115300#comment-14115300
]
Jeff Zhang commented on TEZ-1476:
---------------------------------
[~seth.siddha...@gmail.com], [~jeagles] I notice that after this patch the
vertex status is printed.
2 thoughts:
* Should we add GetVertexStatus to StatusGetOpts as an option for users to
decide whether to print VertexStatus. Because it will print lots of info if dag
has many vertices.
* If VertexStatus is printed, could we add indention in front of VertexStatus
to differentiate DAGStatus.
> 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.1
>
> 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.2#6252)
