Vertica Analytics Platform Version 10.1.x Documentation
Operating System Configuration Task Overview
This topic provides a high-level overview of the OS settings required for Vertica. Each item provides a link to additional details about the setting and detailed steps on making the configuration change. The installer tests for all of these settings and provides hints, warnings, and failures if the current configuration does not meet Vertica requirements.
Before You Install the Operating System
|Supported Platforms||Verify that your servers meet the platform requirements described in Supported Platforms. Unsupported operating systems are detected by the installer.|
|LVM||Vertica Analytic Database supports Linux Volume Manager (LVM) on all supported operating systems. For information on LVM requirements and restrictions, see the section, Vertica Support for LVM.|
Choose the storage format type based on deployment requirements. Vertica recommends the following storage format types where applicable:
For the Vertica I/O profile, the ext4 file system is considerably faster than ext3.
The storage format type at your backup and temporary directory locations must support fcntl lockf (POSIX) file locking.
|Swap Space||A 2GB swap partition is required. Partition the remaining disk space in a single partition under "/".|
|Disk Block Size||The disk block size for the Vertica data and catalog directories should be 4096 bytes, the default for ext4 file systems.|
|Memory||For more information on sizing your hardware, see the Vertica Hardware Planning Guide.|
|Firewall/Ports||Firewalls, if present, must be configured so as not to interfere with Vertica.|
General Operating System Configuration - Automatically Configured by Installer
These general OS settings are automatically made by the installer if they do not meet Vertica requirements. You can prevent the installer from automatically making these configuration changes by using the
--no-system-configuration parameter for the
|Nice Limits||The database administration user must be able to nice processes back to the default level of 0.|
|User Open Files Limit||The open file limit for the dbadmin user should be at least 1 file open per MB of RAM, 65536, or the amount of RAM in MB; whichever is greater.|
|System Open File Limits||The maximum number of files open on the system must not be less than at least the amount of memory in MB, but not less than 65536.|
/etc/pam.d/su must contain the line:
This allows for the conveying of limits to commands run with the
|Address Space Limits||The address space limits (
|File Size Limits||The file sizelimits (
|User Process Limits||The
|Maximum Memory Maps||The vm.max_map_count in /etc/sysctl.conf must be 65536 or the amount of memory in KB / 16, whichever is greater.|
General Operating System Configuration - Manual Configuration
The following general OS settings must be done manually.
|Disk Readahead||This disk readahead must be at least 2048, with a high of 8192. Set this high limit only with the help of Vertica support. The specific value depends on your hardware configuration.|
|NTP Services||The NTP daemon must be enabled and running, with the exception of Red Hat 7 and CentOS 7 systems.|
|chrony||For Red Hat 7 and CentOS 7 systems, chrony must be enabled and running.|
|SELinux||SElinux must be disabled or run in permissive mode.|
|CPU Frequency Scaling||
Vertica recommends that you disable CPU Frequency Scaling.
Your systems may use significantly more energy when CPU frequency scaling is disabled.
For Red Hat 7, CentOS 7 and Amazon Linux 2.0, Transparent Hugepages must be set to always.
For all other operating systems, Transparent Hugepages must be disabled or set to madvise.
The I/O Scheduler for disks used by Vertica must be set to deadline or noop.
|Support Tools||Several optional packages can be installed to assist Vertica support when troubleshooting your system.|
System User Requirements
The following tasks pertain to the configuration of the system user required by Vertica.
|System User Requirements||The installer automatically creates a user with the correct settings. If you specify a user with
|LANG Environment Settings||The LANG environment variable must be set and valid for the database administration user.|
|TZ Environment Settings||The TZ environment variable must be set and valid for the database administration user.|
Was this topic helpful?