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

Ayush Saxena updated TEZ-4605:
------------------------------
    Summary:  Enable hadoop CallerContext in TezChild and DAGAppMaster   (was: 
enable hadoop CallerContext 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
>            Assignee: liang yu
>            Priority: Major
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to