1 概述

本文档描述CENTOS7.2操作系统部署CDH企业版的过程。Cloudera企业级数据中心的安装主要分为4个步骤：

1.集群服务器配置，包括安装操作系统、关闭防火墙、同步服务器时钟等；

2.外部数据库安装

3.安装Cloudera管理器；

4.安装CDH集群；

集群完整性检查，包括HDFS文件系统、MapReduce、Hive等是否可以正常运行。

这篇文档将着重介绍Cloudera管理器与CDH的安装，并基于以下假设：

操作系统版本：CENTOS7.2
MariaDB数据库版本为10.2.1
CM版本：CDH 5.10.0
CDH版本：CDH 5.10.0

5.采用ec2-user对集群进行部署

6.您已经下载CDH和CM的安装包

2 前期准备

2.1 hostname及hosts配置

集群中各个节点之间能互相通信使用静态IP地址。IP地址和主机名通过/etc/hosts配置，主机名/etc/hostname进行配置。

以cm节点（172.31.2.159）为例：

hostname配置

/etc/hostname文件如下：

| ip-172-31-2-159 |

|:----|

或者你可以通过命令修改立即生效

| ec2-user@ip-172-31-2-159 ~$ sudo hostnamectl set-hostname ip-172-31-2-159 |

|:----|

注意：这里修改hostname跟REDHAT6的区别

hosts配置

/etc/hosts文件如下:

| 172.31.2.159 ip-172-31-2-159172.31.12.108 ip-172-31-12-108172.31.5.236 ip-172-31-5-236172.31.7.96 ip-172-31-7-96 |

|:----|

以上两步操作，在集群中其它节点做相应配置。

2.2 禁用SELinux

在所有节点执行sudo setenforce 0 命令，此处使用批处理shell执行：

| ec2-user@ip-172-31-2-159 ~$ sh ssh_do_all.sh node.list "sudo setenforce 0" |

|:----|

集群所有节点修改/etc/selinux/config文件如下：

| SELINUX=disabledSELINUXTYPE=targeted |

|:----|

2.3 关闭防火墙

集群所有节点执行 sudo systemctl stop命令，此处通过shell批量执行命令如下：

2.4 集群时钟同步

在CentOS7.2的操作系统上，已经默认的安装了chrony，配置chrony时钟同步，将cm（172.31.2.159）服务作为本地chrony服务器，其它3台服务器与其保持同步，配置片段：

172.31.2.159配置与自己同步

集群其它节点：在注释下增加如下配置

重启所有机器的chrony服务

| ec2-user@ip-172-31-2-159 ~$ sh ssh_do_all.sh node.list "sudo systemctl restart chronyd" |

|:----|

验证始终同步，在所有节点执行chronycsources命令，如下使用脚本批量执行

| ec2-user@ip-172-31-2-159 ~$ sh ssh_do_all.sh node.list "chronyc sources" |

|:----|

2.5 配置操作系统repo

挂载操作系统iso文件

配置操作系统repo

2.6 安装http服务

安装httpd服务

| ec2-user@ip-172-31-2-159 ~$ sudo yum -y install httpd |

|:----|

启动或停止httpd服务

| ec2-user@ip-172-31-2-159 ~$ sudo systemctl start httpdec2-user@ip-172-31-2-159 ~$ sudo systemctl stop httpd |

|:----|

安装完httpd后，重新制作操作系统repo，换成http的方式方便其它服务器也可以访问

2.7 安装MariaDB

由于centos7默认使用的是5.5.52版本的MariaDB，此处使用的10.2.1版本（http://yum.mariadb.org/10.2.1/centos7-amd64/rpms/），在官网下载rpm安装包：

    MariaDB-10.2.1-centos7-x86_64-client.rpm

    MariaDB-10.2.1-centos7-x86_64-common.rpm

    MariaDB-10.2.1-centos7-x86_64-compat.rpm

    MariaDB-10.2.1-centos7-x86_64-server.rpm

将包下载到本地，放在同一目录，执行createrepo命令生成rpm元数据。

此处使用apache2，将上述mariadb10.2.1目录移动到/var/www/html目录下, 使得用户可以通过HTTP访问这些rpm包。

启动并配置MariaDB

[ec2-user@ip-172-31-2-159 ~]$ sudo systemctl  start mariadb

[ec2-user@ip-172-31-2-159 ~]$ sudo /usr/bin/mysql_secure_installation

 

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS  RECOMMENDED FOR ALL MariaDB

       SERVERS IN PRODUCTION USE!   PLEASE READ EACH STEP CAREFULLY!

 

In order to log into MariaDB to secure it, we'll  need the current

password for the root user.  If you've just installed MariaDB, and

you haven't set the root password yet, the  password will be blank,

so you should just press enter here.

 

Enter current password for root (enter for none):  

OK, successfully used password, moving on...

 

Setting the root password ensures that nobody can  log into the MariaDB

root user without the proper authorisation.

 

Set root password? [Y/n] Y

New password:

Re-enter new password:

Password updated successfully!

Reloading privilege tables..

 ...  Success!

 

 

By default, a MariaDB installation has an  anonymous user, allowing anyone

to log into MariaDB without having to have a user  account created fo

them.  This  is intended only for testing, and to make the installation

go a bit smoother.  You should remove them before moving into a

production environment.

 

Remove anonymous users? [Y/n] Y

 ...  Success!

 

Normally, root should only be allowed to connect  from 'localhost'.  This

ensures that someone cannot guess at the root  password from the network.

 

Disallow root login remotely? [Y/n] n

 ...  skipping.

 

By default, MariaDB comes with a database named  'test' that anyone can

access.   This is also intended only for testing, and should be removed

before moving into a production environment.

 

Remove test database and access to it? [Y/n] Y

 - Dropping  test database...

 ...  Success!

 - Removing  privileges on test database...

 ...  Success!

 

Reloading the privilege tables will ensure that  all changes made so fa

will take effect immediately.

 

Reload privilege tables now? [Y/n] Y

 ...  Success!

 

Cleaning up...

 

All done!   If you've completed all of the above steps, your MariaDB

installation should now be secure.


Thanks for using MariaDB!