question Re: After upgrading to Ambari .2.2.1 container-executor.cfg is always overwritten by a template container-executor.cfg.j2 in Support Questions

After upgrading to Ambari .2.2.1 container-executor.cfg is always overwritten by a template container-executor.cfg.j2

ran — Thu, 14 Apr 2016 19:49:08 GMT

After upgrading to Ambari 2.2.1 When restarting NodeManager ambari overwrites the container-executor.cfg with a template in file container-executor.cfg.j2 .

This template is wrong and causing the yarn to failed any job because the min user is 1000.

Re: After upgrading to Ambari .2.2.1 container-executor.cfg is always overwritten by a template container-executor.cfg.j2

pminovic — Thu, 14 Apr 2016 21:45:47 GMT

Hi @Ran Postar You can reduce "Minimum user ID for submitting job" (min_user_id) in yarn-env in Ambari->Yarn from default 1000 to a smaller value, for example 500. The value is referenced as min.user.id={{min_user_id}} in container-executor.cfg.j2 and it should work.

Re: After upgrading to Ambari .2.2.1 container-executor.cfg is always overwritten by a template container-executor.cfg.j2

ran — Thu, 14 Apr 2016 21:53:45 GMT

Hey @Predrag Minovic, thanks for the quick replay.

How can I add allowed.system.users=yarn,admin , and change the banned.users .

Re: After upgrading to Ambari .2.2.1 container-executor.cfg is always overwritten by a template container-executor.cfg.j2

pminovic — Thu, 14 Apr 2016 22:31:11 GMT

It's not recommended to change banned.users and allowed.system.user for security reasons. It's always a good idea to run Yarn jobs as an end user. It's like when you have real users on the cluster, you create their accounts and let them login and run their apps. yarn user is used to manage Yarn, for example by running "yarn rmadmin" and other such commands. If nevertheless you want to try, the only way is to edit the cfj.j2 file located at /var/lib/ambari-server/resources/common-services/YARN/2.1.0.2.0/package/templates/container-executor.cfg.j2.