Thanks Sumit and Ted. After configuring LinuxContainerExecutor and cgroup. NodeManager sees the container being launched as test user, but Slider process is started as nobody. My cluster does not have Kerberos enabled. In Mapreduce v1, using Linux Task Controller, the child process could run as the client user. It looks like YARN does not starting the container as client user, if Kerberos is not turned on.
I setup kerberos, then containers run as the client user. Thank you all. regards, Eric On Fri, Feb 20, 2015 at 10:38 AM, Ted Yu <[email protected]> wrote: > Discussed with Sumit. > > The ability to start as a different user is better implemented by YARN, > instead of Slider. > > Cheers > > On Fri, Feb 20, 2015 at 9:42 AM, Sumit Mohanty <[email protected]> > wrote: > > > As the agent does not run as root (either as YARN user on non-secured or > > the principal that started on secured), Slider has not implemented the > > ability to start as a different user. > > > > -Sumit > > ________________________________________ > > From: Eric Yang <[email protected]> > > Sent: Friday, February 20, 2015 9:23 AM > > To: [email protected] > > Subject: start service as another user > > > > Hi all, > > > > What is the proper way to start application as another user other than > > YARN? > > > > In python script, I ran it like this: > > > > Execute ( daemon_cmd, > > user = serviceUser > > ) > > > > But it still get executed as yarn user instead of serviceUser. > > > > Thanks > > > > regards, > > Eric > > >
