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

Posted to yarn-issues@hadoop.apache.org by "Dinesh Chitlangia (Jira)" <ji...@apache.org> on 2024/04/09 02:54:00 UTC

[jira] [Resolved] (YARN-11670) Add CallerContext in NodeManager

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

Dinesh Chitlangia resolved YARN-11670.
--------------------------------------
    Fix Version/s: 3.5.0
       Resolution: Fixed

Thanks [~yangjiandan] for contribution and [~whbing]  and [~slfan1989]  for reviews.

> Add CallerContext in NodeManager
> --------------------------------
>
>                 Key: YARN-11670
>                 URL: https://issues.apache.org/jira/browse/YARN-11670
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>            Reporter: Jiandan Yang 
>            Assignee: Jiandan Yang 
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.5.0
>
>
> Currently, MR and Spark have added caller context, enabling tracing of HDFS/ResourceManager operators from Spark apps and MapReduce apps. However, operators from NodeManagers cannot be identified in the audit log. For example, HDFS operations issued from NodeManagers during resource localization cannot be identified.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org