修改主机名

hostnamectl set-hostname ryze-.bigdata.com

然后在 /etc/hosts 文件中配置相关机器的域名 和 域名简写

x.x.x.x ryze-.bigdata.com ryze-

x.x.x.x zed-.bigdata.com  zed-

x.x.x.x zed-.bigdata.com  zed-

并且测试其能互通

配置 /etc/sysconfig/network

HOSTNAME=foo-.example.com

验证配置

uname -a 需要和 hostname 得到一致的域名

# 防火墙关闭

iptables-save > /root/firewall.rules

sudo chkconfig iptables off

sudo service iptables stop

yum install ntp

设置一个同步时间服务器

/etc/ntp.conf

# 笔者使用的 aliyun 这里应该是可以跳过的，我检查了安装 ntp 之后，里面配置了非常多 aliyun 的相关节点。

server .pool.ntp.org

server .pool.ntp.org

server .pool.ntp.org

# 开启 NTP 服务

sudo systemctl start ntpd

# 配置 NTP 服务自启动

sudo systemctl enable ntpd

# 向某个服务器同步时间

ntpdate -u <ntp_server>

# 同步系统时间
hwclock --systohc

wget https://archive.cloudera.com/cm6/6.0.1/redhat7/yum/cloudera-manager.repo -P /etc/yum.repos.d/

# Import the repository signing GPG key

sudo rpm --import https://archive.cloudera.com/cm6/6.0.0/redhat7/yum/RPM-GPG-KEY-cloudera

# yum 安装

sudo yum install oracle-j2sdk1.

# 自己下载包安装

tar xvfz /path/to/jdk-8u<update_version>-linux-x64.tar.gz -C /usr/java/

注意不能更换路径

这里如果使用 yum 安装 cloudera 的源的话会安装 1.8u141 并且会补充一个文件

需要注意一下，Java1.8u161 以上的版本似乎不受影响。

sudo yum install cloudera-manager-daemons cloudera-manager-agent cloudera-manager-server

警告如果没有证书，就不要配这个否则后面会出现 agent 无法上报的问题。

然后配置 auto TSL

sudo JAVA_HOME=/usr/java/jdk1..0_141-cloudera /opt/cloudera/cm-agent/bin/certmanager setup --configure-services

That's it! When you start Cloudera Manager Server, it will have TLS enabled, and all hosts that you add to the cluster, as well as any supported services, will automatically have TLS configured and enabled.

# 安装数据库大礼包

wget http://repo.mysql.com/mysql-community-release-el7-5.noarch.rpm

sudo rpm -ivh mysql-community-release-el7-.noarch.rpm

sudo yum update

sudo yum install mysql-server

sudo systemctl start mysqld

# 然后开始数据库配置

sudo systemctl stop mysqld

# 拷贝日志文件

Move old InnoDB log files /var/lib/mysql/ib_logfile0 and /var/lib/mysql/ib_logfile1 out of /var/lib/mysql/ to a backup location

# 配置数据库文件 /etc/my.conf

[mysqld]

datadir=/var/lib/mysql

socket=/var/lib/mysql/mysql.sock

transaction-isolation = READ-COMMITTED

# Disabling symbolic-links is recommended to prevent assorted security risks;

# to do so, uncomment this line:

symbolic-links = 

key_buffer_size = 32M

max_allowed_packet = 32M

thread_stack = 256K

thread_cache_size =

query_cache_limit = 8M

query_cache_size = 64M

query_cache_type = 

max_connections =

#expire_logs_days =

#max_binlog_size = 100M

#log_bin should be on a disk with enough free space.

#Replace '/var/lib/mysql/mysql_binary_log' with an appropriate path for your

#system and chown the specified folder to the mysql user.

log_bin=/var/lib/mysql/mysql_binary_log

#In later versions of MySQL, if you enable the binary log and do not set

#a server_id, MySQL will not start. The server_id must be unique within

#the replicating group.

server_id=

binlog_format = mixed

read_buffer_size = 2M

read_rnd_buffer_size = 16M

sort_buffer_size = 8M

join_buffer_size = 8M

# InnoDB settings

innodb_file_per_table =

innodb_flush_log_at_trx_commit  =

innodb_log_buffer_size = 64M

innodb_buffer_pool_size = 4G

innodb_thread_concurrency =

innodb_flush_method = O_DIRECT

innodb_log_file_size = 512M

[mysqld_safe]

log-error=/var/log/mysqld.log

pid-file=/var/run/mysqld/mysqld.pid

sql_mode=STRICT_ALL_TABLES

# 添加到自启动项

sudo systemctl enable mysqld

# 重新将 MySQL 启动起来

sudo systemctl start mysqld

# Download the MySQL JDBC driver from http://www.mysql.com/downloads/connector/j/5.1.html (in .tar.gz format). As of the time of writing, you can download version 5.1.46 using wget as follows:

wget https://dev.mysql.com/get/Downloads/Connector-J/mysql-connector-java-5.1.46.tar.gz

# Extract the JDBC driver JAR file from the downloaded file. For example:

tar zxvf mysql-connector-java-5.1..tar.gz

# Copy the JDBC driver, renamed, to /usr/share/java/. If the target directory does not yet exist, create it. For example:

sudo mkdir -p /usr/share/java/

cd mysql-connector-java-5.1.

sudo cp mysql-connector-java-5.1.-bin.jar /usr/share/java/mysql-connector-java.jar

CREATE DATABASE scm DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;

CREATE DATABASE amon DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;

CREATE DATABASE rman DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;

CREATE DATABASE hue DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;

CREATE DATABASE metastore DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;

CREATE DATABASE sentry DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;

CREATE DATABASE nav DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;

CREATE DATABASE navms DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;

CREATE DATABASE oozie DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;

GRANT ALL ON scm.* TO 'scm'@'%' IDENTIFIED BY 'scm';

GRANT ALL ON amon.* TO 'amon'@'%' IDENTIFIED BY 'amon';

GRANT ALL ON rman.* TO 'rman'@'%' IDENTIFIED BY 'rman';

GRANT ALL ON hue.* TO 'hue'@'%' IDENTIFIED BY 'hue';

GRANT ALL ON metastore.* TO 'metastore'@'%' IDENTIFIED BY 'metastore';

GRANT ALL ON sentry.* TO 'sentry'@'%' IDENTIFIED BY 'sentry';

GRANT ALL ON nav.* TO 'nav'@'%' IDENTIFIED BY 'nav';

GRANT ALL ON navms.* TO 'navms'@'%' IDENTIFIED BY 'navms';

GRANT ALL ON oozie.* TO 'oozie'@'%' IDENTIFIED BY 'oozie';

Example : Running the script when MySQL or MariaDB is installed on another host

This example demonstrates how to run the script on the Cloudera Manager Server host (cm01.example.com) and connect to a remote MySQL or MariaDB host (db01.example.com):

sudo /opt/cloudera/cm/schema/scm_prepare_database.sh mysql -h db01.example.com --scm-host cm01.example.com scm scm

Enter database password:

JAVA_HOME=/usr/java/jdk1..0_141-cloudera

Verifying that we can write to /etc/cloudera-scm-server

Creating SCM configuration file in /etc/cloudera-scm-server

Executing:  /usr/java/jdk1..0_141-cloudera/bin/java -cp /usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/java/postgresql-connector-java.jar:/opt/cloudera/cm/schema/../lib/* com.cloudera.enterprise.dbutil.DbCommandExecutor /etc/cloudera-scm-server/db.properties com.cloudera.cmf.db.

[                          main] DbCommandExecutor              INFO  Successfully connected to database.

All done, your SCM database is configured correctly!

# start cloudera-scm-server

sudo systemctl start cloudera-scm-server

# 通过该命令观察启动流程

sudo tail -f /var/log/cloudera-scm-server/cloudera-scm-server.log

当看到

INFO WebServerImpl:com.cloudera.server.cmf.WebServerImpl: Started Jetty server.

the Cloudera Manager Admin Console is ready

然后就可以通过 ip: 上去了

Range Definition    Matching Hosts

10.1..[-]    10.1.1.1, 10.1.1.2, 10.1.1.3, 10.1.1.4

host[-].example.com    host1.example.com, host2.example.com, host3.example.com

host[-].company.com    host07.example.com, host08.example.com, host09.example.com, host10.example.com

Note: Unqualified hostnames (short names) must be unique in a Cloudera Manager instance. For example, you cannot have both host01.example.com and host01.standby.example.com managed by the same Cloudera Manager Server.

You can specify multiple addresses and address ranges by separating them with commas, semicolons, tabs, or blank spaces, or by placing them on separate lines. Use this technique to make more specific searches instead of searching overly wide ranges. Only scans that reach hosts running SSH will be selected for inclusion in your cluster by default. You can enter an address range that spans over unused addresses and then clear the nonexistent hosts later in the procedure, but wider ranges require more time to scan.

已启用透明大页面压缩，可能会导致重大性能问题。请运行“echo never > /sys/kernel/mm/transparent_hugepage/defrag”和
“echo never > /sys/kernel/mm/transparent_hugepage/enabled”以禁用此设置，然后将同一命令添加到 /etc/rc.local 等初始化脚本中，以便在系统重启时予以设置。以下主机将受到影

Starting with CDH 6, PostgreSQL-backed Hue requires the Psycopg2 version to be at least 2.5.4, see the documentation for more information. 
This warning can be ignored if hosts will not run CDH 6, or will not run Hue with PostgreSQL. The following hosts have an incompatible Psycopg2 version of '2.5.1':