when you edit container-executor.cfg on a non-ambari managed cluster what services do you need to restart?

[#1]

more specifically, we'd like to change min.user.id in container-executor.cfg

[#2]

I think restarting node mangers will be suffice here.

[#3 · Accepted solution]

To be on the safe side you can restart all Yarn related components. Also note that min.user.id and container-executor.cfg will be used only with Yarn secure containers, meaning, on Linux

yarn.nodemanager.container-executor.class=org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor

or LCE, and WSCE on Windows.

[#4]

changing min_user_id in Ambari requires restarting the following: App Timeline Server, NodeManager, ResourceManager, YARN Client and since I had Oozie enabled, that too had stale configs.