For Files View to
access HDFS, the Ambari Server daemon hosting the view needs to act as the proxy user for
HDFS.
This allows Ambari to submit requests to HDFS on behalf of
Files View users.If you are running views in an operational Ambari server (one that is
operating the cluster) Ambari does this setup by default. You should verify that the
setup described in the following subsections has been completed. If you are running
views on a standalone server, you must setup proxy user settings manually.
To set
up an HDFS proxy user for the Ambari Server daemon account, you need to configure the
proxy user in the HDFS configuration. This configuration is determined by the account
name the ambari-server daemon is running as. For example, if your ambari-server is
running as root, you set up an HDFS proxy user for root with the
following:
-
In Ambari Web, browse to .
-
On the Advanced tab, browse to the Custom
core-site section.
-
Click Add Property…
- Enter the following custom properties:
- hadoop.proxyuser.root.groups="users"
hadoop.proxyuser.root.hosts=ambari-server.hostname
- Notice the ambari-server daemon account name
root is part of the property name. Be sure to modify
this property name for the account name you are running the ambari-server
as. For example, if you were running ambari-server
daemon under the account name ambariusr, you would
use the following properties instead:
- hadoop.proxyuser.ambariusr.groups="users"
hadoop.proxyuser.ambariusr.hosts=ambari-server.hostname
- Similarly, if you have configured Ambari Server for Kerberos, be sure to
modify this property name for the primary Kerberos principal user. For
example, if ambari-server is setup for Kerberos using principal
ambari-server@EXAMPLE.COM, you would use the
following properties instead:
- hadoop.proxyuser.ambari-server.groups="users"
hadoop.proxyuser.ambari-server.hosts=ambari-server.hostname
-
Save the configuration change.
Restart the required components as prompted by Ambari.
