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

Posted to issues@tez.apache.org by "liang yu (Jira)" <ji...@apache.org> on 2025/02/20 08:07:00 UTC

[jira] [Updated] (TEZ-4605) enable hadoop CallerContext in TezChild and DAGAppMaster

     [ https://issues.apache.org/jira/browse/TEZ-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

liang yu updated TEZ-4605:
--------------------------
    Summary: enable hadoop CallerContext in TezChild and DAGAppMaster  (was: enable hadoop CallContext in TezChild and DAGAppMaster)

> enable hadoop CallerContext in TezChild and DAGAppMaster
> --------------------------------------------------------
>
>                 Key: TEZ-4605
>                 URL: https://issues.apache.org/jira/browse/TEZ-4605
>             Project: Apache Tez
>          Issue Type: New Feature
>            Reporter: liang yu
>            Priority: Major
>
> Currently, MR and Spark have added caller context, enabling tracing of HDFS/ResourceManager operators from Spark apps and MapReduce apps. However, operators from TEZ apps cannot be identified in the audit log. For example, HDFS operations issued from TEZ AppMaster during listing files cannot be identified.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)