You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2021/08/27 10:53:00 UTC

[jira] [Commented] (TEZ-4333) Debug artifacts can include DAG plan in json format

    [ https://issues.apache.org/jira/browse/TEZ-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405741#comment-17405741 ] 

László Bodor commented on TEZ-4333:
-----------------------------------

https://github.com/apache/tez/pull/149

> Debug artifacts can include DAG plan in json format
> ---------------------------------------------------
>
>                 Key: TEZ-4333
>                 URL: https://issues.apache.org/jira/browse/TEZ-4333
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Major
>
> Currently, tez.generate.debug.artifacts saves a serialized protobuf file, which is hard to read because it just encodes the user payload. At the same time, tez AM logs a readable json file into the tez AM logs but only at DEBUG level. I'm proposing that tez.generate.debug.artifacts could write this readable json into a separated dag json file, this way:
> 1. we can use tez.generate.debug.artifacts to produce one more useful file
> 2. don't have to set AM log level to DEBUG if we're only interested in the dag plan



--
This message was sent by Atlassian Jira
(v8.3.4#803005)