7. Primary CDH User¶
Cloudera supports use of root or sudo user as administration user. If using sudo, user must have full nopassword sudo privileges.
Table of Contents
The following tutorial goes through configuring a new physical machine from scratch. The first section, called “Pre-Configuration”, is a little vague because the information can vary between machines. The second section, called “Base Configuration”, will usually be identical for all machines.
All systems in the cluster must be reachable by DNS or by data in ‘/etc/hosts’.
SELINUX must be disabled:
vi /etc/selinux/config
Change:
SELINUX=enforcing
To:
SELINUX=disabled
Or:
SELINUX=permissive
Note
Systems will need full reboot before changes take effect.
System default yum repos must be functional.
If working behind a proxy, system proxy settings must be configured.
System packages must be syncronized with default repositories:
yum clean all
yum distro-sync
Cloudera supports use of root or sudo user as administration user. If using sudo, user must have full nopassword sudo privileges.
Using the primary CDH user, every system in the cluster must be able to communicate via ssh to all other systems in the cluster.
Set the hostname for each system in the cluster.
Note
Limiting host names to lower-case alphanumeric characters is recommended.
The following definitions must exist in /etc/security/limits.conf
vi /etc/security/limits.conf
* soft nofile 32768
* hard nofile 32768
hadoop - nofile 32768
hadoop - nproc unlimited
hdfs - nofile 32768
hbase - nofile 32768
spark soft nofile 65535
spark hard nofile 65535
spark - nproc 32768
NTP must be installed and properly configured on all cluster systems. Also NTP services should start on system boot:
service ntpd start
chkconfig ntpd on
All systems in cluster must be in time-sync with one-another.
Once all configuration has been done, rebooting all cluster systems is recommended to properly activate all of the changes.