Shulou(Shulou.com)06/01 Report--

This article mainly introduces how to install Vertica database on linux6. It is very detailed and has certain reference value. Friends who are interested must finish reading it.

Database users and permissions

Dbadmin-Administrative user

Verticadba-Group for DBA users

Dbadmin users between cluster nodes need to configure mutual trust.

The username and password should be the same between the cluster nodes.

The shell environment for Dbadmin users is set to / bin/bash because all shell scripts from vertica are executed in the bash shell environment.

Provide read and write access to the following directories:

/ opt/vertica/*

/ home/dbadmin

Prepare the storage path before installation

Specify the directory where catalog files is stored and the directory where data files is stored. Catalog and data files storage paths should be separate and should not be stored together. The storage directory of Catalog should be consistent among all nodes in the cluster. And be careful not to use shared directories to store these two types of files between nodes.

Disk Space Requirements for Vertica

Network configuration

The network configuration of a single node and a cluster is the same, with one exception. If localhost and loopback address (127.0.0.1) are used during installation, it can only be used by a single node. It is not possible to add nodes to become clusters later.

Must be able to log in using the ssh protocol.

Port availability

Port

Protocol

Service

Notes

seven

TCP

Management Console

Required by Management Console to discover Vertica nodes.

twenty-two

TCP

Sshd

Required by Administration Tools and the Management Console Cluster Installation wizard.

5433

TCP

Vertica

Vertica client (vsql, ODBC, JDBC, etc) port.

5434

TCP

Vertica

Intra- and inter-cluster communication. Vertica opens the Vertica client port + 1 (5434 by default) for intra-cluster communication, such as during a plan. If the port + 1 from the default client port is not available, then Vertica opens a random port for intra-cluster communication.

5433

UDP

Vertica

Vertica spread monitoring.

5444

TCP

Vertica

Management Console

MC-to-node and node-to-node (agent) communications port. See Changing MC or Agent Ports.

5450

TCP

Vertica

Management Console

Port used to connect to MC from a web browser and allows communication from nodes to the MC application/web server. See Connecting to Management Console.

4803

TCP

Spread

Client connections.

4803

UDP

Spread

Daemon to Daemon connections.

4804

UDP

Spread

Daemon to Daemon connections.

6543

UDP

Spread

Monitor to Daemon connection.

Firewall Settin

Rhel6/centos6

# service iptables save# service iptables stop# chkconfig iptables off# service ip6tables save# service ip6tables stop# chkconfig ip6tables off

General Operating System Configuration-Automatically Configured by the Installer

General Operating System Configuration-Manual Configuration

System User Configuration

Rpm package installation openssh-Required for Administration Tools connectivity between nodes.which-Required for Vertica operating system integration and for validating installations.dialog-Required for interactivity with Administration Tools.# yum install openssh# yum install which# yum install dialogTZ variable setting

If the TZ variable is not set, the installation will report an error S0305.

Automatically modified operating system parameters

These general Operating System 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-configurationparameter for theinstall_verticascript.

If the following parameters do not meet the vertica requirements, they will be automatically modified during installation. If you don't want to be automatically modified, you can skip it with the-- no-system-configuration parameter.

Sysctl

Nice Limits Configuration

Min_free_kbytes Setting

User Max Open Files Limit

System Max Open Files Limit

Pam Limits

Pid_max Setting

User Address Space Limits

User File Size Limit

User Process Limit

Maximum Memory Maps Configuration

Manually modified operating system parameters

The following general Operating System settings must be done manually.

Manually Configuring Operating System Settings

Check for Swappiness

Disk Readahead

Enabling Network Time Protocol (NTP)

Enabling chrony or ntpd for Red Hat 7/CentOS 7 Systems

SELinux Configuration

CPU Frequency Scaling

Enabling or Disabling Transparent Hugepages

Disabling Defrag for Red Hat and CentOS Systems

I/O Scheduling

Support Tools

Install a single-node vertica database below:

Casually install a test environment for fun, many of them are not carefully studied.

Operating system version:

[root@ verticatest] # lsb_release-a

LSB Version:: base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch

Distributor ID: RedHatEnterpriseServer

Description: Red Hat Enterprise Linux Server release 6.4 (Santiago)

Release: 6.4

Codename: Santiago

Operating system time zone:

[root@verticatest ~] # more / etc/sysconfig/clock

ZONE= "Asia/Shanghai"

Install the rpm package:

[root@verticatest ~] # yum install openssh ntp which dialog-y

[root@verticatest ~] # service ntpd restart

Shutting down ntpd: [FAILED]

Starting ntpd: [OK]

[root@verticatest ~] # chkconfig ntpd on

Firewall permissions:

Service iptables saveservice iptables stopchkconfig iptables offservice ip6tables saveservice ip6tables stopchkconfig ip6tables off

Selinux settings:

[root@verticatest ~] # more / etc/selinux/config

# This file controls the state of SELinux on the system.

# SELINUX= can take one of these three values:

# enforcing-SELinux security policy is enforced.

# permissive-SELinux prints warnings instead of enforcing.

# disabled-No SELinux policy is loaded.

SELINUX=disabled

# SELINUXTYPE= can take one of these two values:

# targeted-Targeted processes are protected

# mls-Multi Level Security protection.

SELINUXTYPE=targeted

[root@verticatest ~] # setenforce 0

Setenforce: SELinux is disabled

Other configurations:

Echo deadline > / sys/block/sda/queue/scheduler

Echo never > / sys/kernel/mm/redhat_transparent_hugepage/enabled

Echo never > / sys/kernel/mm/redhat_transparent_hugepage/defrag

Echo no > / sys/kernel/mm/redhat_transparent_hugepage/khugepaged/defrag

Echo 0 > / proc/sys/vm/swappiness

/ sbin/blockdev-- setra 8192 / dev/sda

Ssh configuration

LoginGraceTime 0

[root@verticatest ~] # service sshd reload

Reloading sshd:

Create a user:

[root@verticatest] # groupadd-g 601 verticadba

[root@verticatest] # useradd-u 601-g 601 dbadmin

[root@verticatest ~] # mkdir-p / home/dbadmin/ data ^ C

[root@verticatest ~] # echo oracle | passwd-- stdin dbadmin

Changing password for user dbadmin.

Passwd: all authentication tokens updated successfully.

[root@ verticatest ~] # su-dbadmin

[dbadmin@ verticatest] $mkdir-p / home/dbadmin/data

[dbadmin@ verticatest] $mkdir-p / home/dbadmin/catalog

[dbadmin@ verticatest ~] $more .bash _ profile

# .bash _ profile

# Get the aliases and functions

If [- f ~ / .bashrc]; then

. ~ / .bashrc

Fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

Export PATH

Export TZ= "Asia/Shanghai"

[dbadmin@ verticatest] $. .bash _ profile

[dbadmin@ verticatest ~] $echo $TZ

Asia/Shanghai

Install the database software:

[root@verticatest] # / opt/vertica/sbin/install_vertica-- hosts 192.168.117.4-- rpm / root/vertica-8.0.0-0.x86_64.RHEL6.rpm-- dba-user dbadmin

Vertica Analytic Database 8.0.0-0 Installation Tool

> > Validating options...

Mapping hostnames in-- hosts (- s) to addresses...

> > Starting installation tasks.

Getting system information for cluster (this may take a while)...

Default shell on nodes:

192.168.117.4 / bin/bash

Validating software versions (rpm or deb)...

> > Beginning new cluster creation...

Successfully backed up admintools.conf on 192.168.117.4

> > Creating or validating DB Admin user/group...

Successful on hosts (1): 192.168.117.4

Provided DB Admin account details: user = dbadmin, group = verticadba, home = / home/dbadmin

Creating group... Group already exists

Validating group... Okay

Creating user... User already exists

Validating user... Okay

> > Validating node and cluster prerequisites...

System prerequisites passed. Threshold = WARN

> > Establishing DB Admin SSH connectivity...

Installing/Repairing SSH keys for dbadmin

> > Setting up each node and modifying cluster...

Creating Vertica Data Directory...

Updating agent...

Creating node node0001 definition for host 192.168.117.4

... Done

> > Sending new cluster configuration to all nodes...

Starting agent...

> > Completing installation...

Running upgrade logic

No spread upgrade required: / opt/vertica/config/vspread.conf not found on any node

Installation complete.

Please evaluate your hardware using Vertica's validation tools:

Https://my.vertica.com/docs/8.0.x/HTML/index.htm#cshid=VALSCRIPT

To create a database:

1. Logout and login as dbadmin. (see note below)

2. Run / opt/vertica/bin/adminTools as dbadmin

3. Select Create Database from the Configuration Menu

Note: Installation may have made configuration changes to dbadmin

That do not take effect until the next session (logout and login).

To add or remove hosts, select Cluster Management from the Advanced Menu.

Create the database:

[dbadmin@verticatest ~] $/ opt/vertica/bin/admintools

The enterprise version specifies the location of the license file, and the community version determines the ok directly.

Select the up and down keys, and select OK,cancel and help below with the tab key.

The arrow keys select the second line, the space is selected, the tab key selects ok, and press enter.

Select 6 configuration menu

Select 1 Create database:

Enter the name of the database and comments for db:

Enter the password:

Confirm password:

Select the catalog and data file paths:

K-safe is the high availability level of the vertica database cluster:

Creation process:

* Creating database: firstvdb * *

Creating database firstvdb

Starting bootstrap node v_firstvdb_node0001 (192.168.117.4)

Starting nodes:

V_firstvdb_node0001 (192.168.117.4)

Starting Vertica on all nodes. Please wait, databases with large catalog may take a while to initialize.

Node Status: v_firstvdb_node0001: (DOWN)

Node Status: v_firstvdb_node0001: (DOWN)

Node Status: v_firstvdb_node0001: (DOWN)

Node Status: v_firstvdb_node0001: (DOWN)

Node Status: v_firstvdb_node0001: (UP)

Automatically installing extension packages

Package: flextable

Success: package flextable successfully installed

Package: approximate

Success: package approximate successfully installed

Package: hdfsconnector

Success: package hdfsconnector successfully installed

Package: AWS

Success: package AWS successfully installed

Package: logsearch

Success: package logsearch successfully installed

Package: txtindex

Success: package txtindex successfully installed

Package: MachineLearning

Success: package MachineLearning successfully installed

Package: idol

Success: package idol successfully installed

Package: kafka

Success: package kafka successfully installed

Package: place

Success: package place successfully installed

Connect to the database:

[dbadmin@verticatest ~] $vsql-h 192.168.117.4-U dbadmin

Password:

Welcome to vsql, the Vertica Analytic Database interactive terminal.

Type:\ h or\? For help with vsql commands

\ g or terminate with semicolon to execute query

\ q to quit

Dbadmin= >

You can also use a local loopback address here.

The above is all the contents of the article "how to install Vertica column database on linux6". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.