Operating System Requirements
This topic describes the operating system requirements for CDP Private Cloud Base.
CDP Private Cloud Base Supported Operating Systems
Please see the Cloudera Support Matrix for detailed information about supported operating systems.
Operating System support for the CDP Private Cloud Base Trial Installer
SLES 12 SP5 is not supported when using the Using the Trial Installer
(cloudera-manager-installer.bin
) to install Cloudera
Manager.
Important information about Runtime and Cloudera Manager Supported Operating Systems
Runtime provides parcels for select versions of RHEL-compatible operating systems.
Software Dependencies
- Python - Python dependencies for the different CDP components is mentioned below:
- Cloudera Manager
- Cloudera Manager supports the system Python on supported OSes.
- Hue
- Hue requires Python 3.8.
- Spark
- Spark 2.4 supports Python 2.7 and 3.4-3.7.
- Perl - Cloudera Manager requires perl.
- python-psycopg2 - Cloudera Manager 7 has a dependency on the
package
python-psycopg2
. Hue in Runtime 7 requires a higher version ofpsycopg2
than is required by the Cloudera Manager dependency. For more information, see Installing thepsycopg2
Python Package. - iproute package - CDP Private Cloud Base has a dependency on the
iproute
package. Any host that runs the Cloudera Manager Agent requires the package. The required version varies depending on the operating system:Table 1. iproute package Operating System iproute version RHEL 7 Compatible iproute-3.10
Filesystem Requirements
Supported Filesystems
The Hadoop Distributed File System (HDFS) is designed to run on top of an underlying filesystem in an operating system. Cloudera recommends that you use either of the following filesystems tested on the supported operating systems:
- ext3: This is the most tested underlying filesystem for HDFS.
- ext4: This scalable extension of ext3 is supported in more recent Linux releases.
- XFS: This is the default filesystem in RHEL 7.
- S3: Amazon Simple Storage Service
Kudu Filesystem Requirements - Kudu is supported on ext4 and
XFS. Kudu requires a kernel version and filesystem that supports hole
punching. Hole punching is the use of the
fallocate(2)
system call with the
FALLOC_FL_PUNCH_HOLE
option set.
File Access Time
Linux filesystems keep metadata that record when each file was
accessed. This means that even reads result in a write to the disk. To
speed up file reads, Cloudera recommends that you disable this option,
called atime
, using the noatime
mount
option in /etc/fstab
:
/dev/sdb1 /data1 ext4 defaults,noatime 0
Apply the change without rebooting:
mount -o remount /data1
Filesystem Mount Options
The filesystem mount
options have a
sync
option that allows you to write
synchronously.
Using the sync
filesystem mount option reduces
performance for services that write data to disks, such as HDFS, YARN,
Kafka and Kudu. In CDH, most writes are already replicated. Therefore,
synchronous writes to disk are unnecessary, expensive, and do not
measurably improve stability.
NFS and NAS options are not supported for use as DataNode Data Directory mounts, even when using Hierarchical Storage features.
Cloudera supports mounting /tmp
with the noexec
option.
Mounting /tmp
as a filesystem with the noexec
option is
sometimes done as an enhanced security measure to prevent the execution of files stored
there.
Filesystem Requirements
Cloudera Manager automatically sets nproc
configuration in /etc/security/limits.conf
, but this
configuration can be overridden by individual files in
/etc/security/limits.d/
. This can cause problems with
Apache Impala and other components.
Make sure that the nproc
limits are set sufficiently
high, such as 65536
or 262144
.
nscd for Kudu
Although not a strict requirement, it's highly recommended that you
usenscd
to cache both DNS name resolution and static
name resolution for Kudu.