Use the sasep-servers.sh
script with the
-add option to deploy the
SAS Embedded Process installation across all nodes. The SAS Embedded
Process is installed as a Linux service.
Note: If you are running on a cluster
with Kerberos, complete both steps a and b. If you are not running
with Kerberos, complete only step b.
-
If
you are running on a cluster with Kerberos, you must kinit the HDFS
user.
sudo su - root
su - hdfs | hdfs-userid
kinit -kt location of keytab file
user for which you are requesting a ticket
exit
Here is an example:
sudo su - root
su - hdfs
kinit -kt hdfs.keytab hdfs
exit
Note: The default HDFS user is hdfs.
You can specify a different user ID with the -hdfsuser argument
when you run the sasep-servers.sh -add command.
Note: If you are running on a cluster
with Kerberos, a keytab is required when running the sasep-servers.sh
-add command.
Note: You can run klist while you
are running as an HDFS user to check the status of your Kerberos ticket
on the server. Here is an example:
klist
Ticket cache: FILE/tmp/krb5cc_493
Default principal: hdfs@HOST.COMPANY.COM
Valid starting Expires Service principal
06/20/14 09:51:26 06/27/14 09:51:26 krbtgt/HOST.COMPANY.COM@HOST.COMPANY.COM
renew until 06/22/14 09:51:26
-
Run the sasep-servers.sh
script. Review all of the information in this step before running
the script.
cd SASEPHOME/SAS/SASTKInDatabaseServerForHadoop/9.42-1/bin
./sasep-servers.sh -add
Tip
There are many options available
when installing the SAS Embedded Process. We recommend that you review
the script syntax before running it.
For more information,
see
SASEP-SERVERS.SH Script.
During the install process,
the script asks whether you want to start the SAS Embedded Process.
If you choose Y or y,
the SAS Embedded Process is started on all nodes after the install
is complete. If you choose N or n,
you can start the SAS Embedded Process later by running the ./sasep-servers.sh
-start command.
Note: When you enter the sasep-servers.sh
-add command, a user and group named sasep is
created. You can specify a different user and group name with the -epuser and -epgroup arguments
when you enter the sasep-servers.sh -add command.
Note: The sasep-servers.sh script
can be run from any location. You can also add its location to the
PATH environment variable.
Tip
Although you can install the
SAS Embedded Process in multiple locations, the best practice is to
install only one instance. Only one version of the SASEP JAR files
is installed in your
HadoopHome/lib
directory.
Note: The SAS Embedded Process
must be installed on all nodes capable of executing MapReduce
2 tasks. For
MapReduce 2, this would be nodes where a NodeManager is running. Usually,
every DataNode node has a YARN NodeManager
running. By default, the SAS Embedded Process install script (sasep-servers.sh)
discovers the cluster topology and installs the SAS Embedded Process
on all DataNode nodes, including the host node from where you run
the script (the Hadoop master NameNode). This occurs even if a DataNode
is not present. If you want to limit the list of nodes on which you
want the SAS Embedded Process installed, run the sasep-servers.sh
script with the -host <hosts> option.
Note: If you install the SAS Embedded
Process on a large cluster, the SSHD daemon might reach the maximum
number of concurrent connections. The ssh_exchange_identification:
Connection closed by remote host SSHD error might
occur. To work around the problem, edit the /etc/ssh/sshd_config file,
change the MaxStartups option to the number that accommodates your
cluster, and save the file. Then, reload the SSHD daemon by running
the /etc/init.d/sshd reload command.