[jira] [Created] (YARN-9850) document or revert change in which DefaultContainerExecutor no longer propagates NM env to containers

["Steven Rand (Jira)" <ji...@apache.org>]

Steven Rand created YARN-9850:
---------------------------------

             Summary: document or revert change in which DefaultContainerExecutor no longer propagates NM env to containers
                 Key: YARN-9850
                 URL: https://issues.apache.org/jira/browse/YARN-9850
             Project: Hadoop YARN
          Issue Type: Bug
          Components: nodemanager
            Reporter: Steven Rand


After [https://github.com/apache/hadoop/commit/9d4d30243b0fc9630da51a2c17b543ef671d035c], containers launched by the {{DefaultContainerExecutor}} no longer inherit the environment of the NodeManager.

I don't object to the commit (I actually prefer the new behavior), but I do think that it's a notable breaking change, as people may be relying on variables in the NM environment for their containers to behave correctly.

As far as I can tell, we don't currently include this behavior change in the release notes for Hadoop 3, and it's a particularly tricky one to track down, since there's no JIRA ticket for it.

I think that we should at least include this change in the release notes for the 3.0.0 release. Arguably it's worth having the DefaultContainerExecutor set {{inheritParentEnv}} to true when it creates its {{ShellCommandExecutor}} since that preserves the old behavior and is less surprising to users, but I don't feel strongly either way.



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

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