[
https://issues.apache.org/jira/browse/TEZ-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107055#comment-14107055
]
Jonathan Eagles commented on TEZ-1476:
--------------------------------------
[sseth], I've addressed the issues with vertex printing and null dag progress
with the v2 patch. As far as printing at specific intervals, did you want to
keep or remove printing based on progress update? I'd be happy to make that
change as well. Feel free to tweak this patch as you see fit or open a separate
JIRA if a significant refactoring is needed.
> 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
> 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)
