question Re: when you edit container-executor.cfg on a non-ambari managed cluster what services do you need to restart? in Archives of Support Questions (Read Only)

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

aervits — Wed, 04 May 2016 01:11:42 GMT

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

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

rajkumar_singh — Wed, 04 May 2016 01:13:29 GMT

I think restarting node mangers will be suffice here.

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

pminovic — Wed, 04 May 2016 08:21:57 GMT

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.

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

aervits — Wed, 04 May 2016 08:21:58 GMT

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.