You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hadoop.apache.org by Albert Shau <al...@continuuity.com> on 2013/09/11 19:17:48 UTC
Setting user in yarn in 2.1.0
In 2.1.0, the method to set user in the ApplicationSubmissionContext and
ContainerLaunchContext has been removed and is now in the container token.
Does this mean the application will now always run as the user who submits
the application, or is there some other way to set the user now?
Thanks,
Albert
Re: Setting user in yarn in 2.1.0
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Depends on what 'running means'. For all purposes other than launching the user's container process, yes, the user who submits the application is considered - for e.g. ACLs, Nodemanager security etc. In non-secure case when using DefaultContainerExecutor, the container still runs as the user running YARN. In secure case, it will run as the app-submitter.
Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/
On Sep 11, 2013, at 10:17 AM, Albert Shau wrote:
> In 2.1.0, the method to set user in the ApplicationSubmissionContext and ContainerLaunchContext has been removed and is now in the container token. Does this mean the application will now always run as the user who submits the application, or is there some other way to set the user now?
>
> Thanks,
> Albert
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Setting user in yarn in 2.1.0
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Depends on what 'running means'. For all purposes other than launching the user's container process, yes, the user who submits the application is considered - for e.g. ACLs, Nodemanager security etc. In non-secure case when using DefaultContainerExecutor, the container still runs as the user running YARN. In secure case, it will run as the app-submitter.
Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/
On Sep 11, 2013, at 10:17 AM, Albert Shau wrote:
> In 2.1.0, the method to set user in the ApplicationSubmissionContext and ContainerLaunchContext has been removed and is now in the container token. Does this mean the application will now always run as the user who submits the application, or is there some other way to set the user now?
>
> Thanks,
> Albert
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Setting user in yarn in 2.1.0
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Depends on what 'running means'. For all purposes other than launching the user's container process, yes, the user who submits the application is considered - for e.g. ACLs, Nodemanager security etc. In non-secure case when using DefaultContainerExecutor, the container still runs as the user running YARN. In secure case, it will run as the app-submitter.
Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/
On Sep 11, 2013, at 10:17 AM, Albert Shau wrote:
> In 2.1.0, the method to set user in the ApplicationSubmissionContext and ContainerLaunchContext has been removed and is now in the container token. Does this mean the application will now always run as the user who submits the application, or is there some other way to set the user now?
>
> Thanks,
> Albert
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Setting user in yarn in 2.1.0
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Depends on what 'running means'. For all purposes other than launching the user's container process, yes, the user who submits the application is considered - for e.g. ACLs, Nodemanager security etc. In non-secure case when using DefaultContainerExecutor, the container still runs as the user running YARN. In secure case, it will run as the app-submitter.
Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/
On Sep 11, 2013, at 10:17 AM, Albert Shau wrote:
> In 2.1.0, the method to set user in the ApplicationSubmissionContext and ContainerLaunchContext has been removed and is now in the container token. Does this mean the application will now always run as the user who submits the application, or is there some other way to set the user now?
>
> Thanks,
> Albert
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.