On 11 December 2014 at 10:56, liujs3 <[email protected]> wrote:

> Is appConfig.json set hbase user?
> Like site.hbase-site.hbase.superuser:ocean?
>

the user that an app runs on is the user that YARN starts applications on.

1. on an insecure cluster, it will start as a user with the name "mapred"
or "yarn" (usually, if you install ASF hadoop yourself, it runs as whoever
starts the YARN node managers. We pass an environment variable down,
HADOOP_USER, which is automatically picked up by the standard Hadoop HDFS
client to set the username of the user talking to HDFS.

This means that although it is running as a user called "yarn", it is
talking to HDFS as the user who started the job.

2. On an secure cluster, YARN requires a cluster account (i.e. unix or
windows) for every user submitting a job. The client authenticates using
Kerberos, includes the kerberos keytab needed to allow the deployed service
to talk to HDFS and other services (Zookeeper, for example). Slider and its
deployed containers run as you. The keytab is also used by HBase to
authenticate with HDFS.

Summary: if you want isolated per-user applications, you need to run on a
secure cluster. On an insecure cluster, anyone has access to the hbase data
anyway, because HDFS is readable by all.

-- 
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.

Reply via email to