大数据Hadoop集群搭建
大数据Hadoop集群搭建
一、环境
服务器配置：
CPU型号：Intel® Xeon® CPU E5-2620 v4 @ 2.10GHz
CPU核数：16
内存：64GB
操作系统
版本：CentOS Linux release 7.5.1804 (Core)
主机列表：
| IP | 主机名 |
|---|---|
| 192.168.1.101 | node1 |
| 192.168.1.102 | node2 |
| 192.168.1.103 | node3 |
| 192.168.1.104 | node4 |
| 192.168.1.105 | node5 |
软件安装包路径：/data/tools/
JAVA_HOME路径：/opt/java # java为软链接，指向jdk的指定版本
Hadoop集群路径：/data/bigdata/
软件版本及部署分布：
| 组件名 | 安装包 | 说明 | node1 | node2 | node3 | node4 | node5 |
|---|---|---|---|---|---|---|---|
| JDK | jdk-8u162-linux-x64.tar.gz | 基础环境 | ✔ | ✔ | ✔ | ✔ | ✔ |
| zookeeper | zookeeper-3.4.12.tar.gz | ✔ | ✔ | ✔ | |||
| Hadoop | hadoop-2.7.6.tar.gz | ✔ | ✔ | ✔ | ✔ | ✔ | |
| spark | spark-2.1.2-bin-hadoop2.7.tgz | ✔ | ✔ | ✔ | ✔ | ✔ | |
| scala | scala-2.11.12.tgz | ✔ | ✔ | ✔ | ✔ | ✔ | |
| hbase | hbase-1.2.6-bin.tar.gz | ✔ | ✔ | ✔ | |||
| hive | apache-hive-2.3.3-bin.tar.gz | ✔ | |||||
| kylin | apache-kylin-2.3.1-hbase1x-bin.tar.gz | ✔ | |||||
| kafka | kafka_2.11-1.1.0.tgz | ✔ | ✔ | ||||
| hue | hue-3.12.0.tgz | ✔ | |||||
| flume | apache-flume-1.8.0-bin.tar.gz | ✔ | ✔ | ✔ | ✔ | ✔ |
注：所有的软链接不可以跨服务器传输，应该单独创建；否则会把软链接所指向的文件或整个目录传过去；
二、常用命令
1、查看系统基本配置：
[root@localhost ~]# uname -a
Linux node1 3.10.0-123.9.3.el7.x86_64 #1 SMP Thu Nov 6 15:06:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost ~]# cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
[root@localhost ~]# free -m
total used free shared buffers cached
Mem: 64267 2111 62156 16 212 1190
-/+ buffers/cache: 708 63559
Swap: 32000 0 32000
[root@localhost ~]# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 16
On-line CPU(s) list: 0-15
Thread(s) per core: 2
Core(s) per socket: 8
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
Stepping: 1
CPU MHz: 2095.148
BogoMIPS: 4190.29
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 20480K
NUMA node0 CPU(s): 0-15
[root@localhost ~]# df -h
文件系统 容量 已用 可用 已用% 挂载点
/dev/sda2 100G 3.1G 97G 4% /
devtmpfs 7.7G 0 7.7G 0% /dev
tmpfs 7.8G 0 7.8G 0% /dev/shm
tmpfs 7.8G 233M 7.5G 3% /run
tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/sda1 500M 9.8M 490M 2% /boot/efi
/dev/sda4 1.8T 9.3G 1.8T 1% /data
tmpfs 1.6G 0 1.6G 0% /run/user/1000
2、启动集群
start-dfs.sh
start-yarn.sh
3、关闭集群
stop-yarn.sh
stop-dfs.sh
4、监控集群
hdfs dfsadmin -report
5、单个进程启动/关闭
hadoop-daemon.sh start|stop namenode|datanode| journalnode
yarn-daemon.sh start |stop resourcemanager|nodemanager
三、 环境准备（所有服务器）
1、设置主机名（其它类似）
[root@localhost ~]# hostnamectl set-hostname node1
2、关闭防火墙firewalld并禁止开机自启动和SELINUX
[root@node1 ~]# systemctl disable firewalld.service
[root@node1 ~]# systemctl stop firewalld.service
[root@node1 ~]# systemctl status firewalld.service
● firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:firewalld(1)
[root@node1 ~]# setenforce 0
[root@node1 ~]# sed -i 's#SELINUX=enforcing#SELINUX=disabled#g' /etc/selinux/config
[root@node1 ~]# grep SELINUX=disabled /etc/selinux/config
SELINUX=disabled
3、修改hosts文件
[root@node1 ~]# vim /etc/hosts
#127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
#::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.101 node1
192.168.1.102 node2
192.168.1.103 node3
192.168.1.104 node4
192.168.1.105 node5
4、设置ssh免密登陆,可用ansible
[root@node1 ~]# ssh-keygen -t rsa -P '' -f ~/.ssh/id_rsa
[root@node1 ~]# cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys
[root@node1 ~]# ll -d .ssh/
drwx------ 2 root root 4096 Jun 5 08:50 .ssh/
[root@node1 ~]# ll .ssh/
total 12
-rw-r--r-- 1 root root 599 Jun 5 08:50 authorized_keys
-rw------- 1 root root 672 Jun 5 08:50 id_dsa
-rw-r--r-- 1 root root 599 Jun 5 08:50 id_dsa.pub
# 把其它服务器的~/.ssh/id_dsa.pub内容也追加到node1服务器的~/.ssh/authorized_keys文件中，然后分发
[root@node1 ~]# scp –rp ~/.ssh/authorized_keys node2: ~/.ssh/
[root@node1 ~]# scp –rp ~/.ssh/authorized_keys node3: ~/.ssh/
[root@node1 ~]# scp –rp ~/.ssh/authorized_keys node4: ~/.ssh/
[root@node1 ~]# scp –rp ~/.ssh/authorized_keys node5: ~/.ssh/
也可以node1生成一套密钥，然后把~/.ssh整个目录分发到其它服务器，共用一个密钥
5、修改文件句柄数
[root@node1 ~]# vim /etc/security/limits.conf
#---------custom-----------------------
#
* soft nofile 240000
* hard nofile 655350
* soft nproc 240000
* hard nproc 655350
#-----------end-----------------------
[root@node1 ~]# source /etc/security/limits.conf
[root@node1 ~]# ulimit -n
24000
6、时间同步
ntp服务器设置
# 局域网内设置一台ntp服务器，其它和这台ntp同步即可，云服务器一般默认已同步
[root@node1 ~]# yum install ntp -y # 安装ntp服务
[root@node1 ~]# cp -a /etc/ntp.conf{,.bak}
[root@node1 ~]# vim /etc/ntp.conf
restrict default kod nomodify notrap nopeer noquery # restrict、default定义默认访问规则，nomodify禁止远程主机修改本地服务器
restrict 127.0.0.1 # 这里的查询是服务器本身状态的查询。
restrict -6 ::1
#server 0.centos.pool.ntp.org iburst # 注掉官方自带的网络站点
#server 1.centos.pool.ntp.org iburst
#server 2.centos.pool.ntp.org iburst
#server 3.centos.pool.ntp.org iburst
server ntp1.aliyun.com # 目标服务器网络位置
server 127.127.1.0 # local clock,当服务器与公用的时间服务器失去联系时，就是连不上互联网时，以局域网内的时间服务器为客户端提供时间同步服务。
fudge 127.127.1.0 stratum 10
# 如果计划任务有时间同步，先注释，两种用法会冲突。
[root@node1 ~]# crontab –e
#*/30 * * * * /usr/sbin/ntpdate ntp1.aliyun.com > /dev/null 2>&1;/sbin/hwclock -w
# 启动服务并设置开启自启:
[root@node1 /]# systemctl start ntpd.service # 启动服务
[root@node1 /]# systemctl enable ntpd.service # 设置为开机启动
[root@node1 ~]# systemctl status ntpd.service
● ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; disabled; vendor preset: disabled)
Active: active (running) since 一 2018-05-21 13:47:33 CST; 1 weeks 2 days ago
Main PID: 17915 (ntpd)
CGroup: /system.slice/ntpd.service
└─17915 /usr/sbin/ntpd -u ntp:ntp -g
5月 23 11:41:40 node1 ntpd[17915]: Listen normally on 14 enp0s25 192.168.1.101 UDP 123
5月 23 11:41:40 node1 ntpd[17915]: new interface(s) found: waking up resolver
5月 23 11:41:42 node1 ntpd[17915]: Listen normally on 18 enp0s25 fe80::6a85:bbb1:ad57:f6ae UDP 123
[root@node1 ~]# ntpq -p # 检查时间服务器是否正确同步
remote refid st t when poll reach delay offset jitter
==============================================================================
*time5.aliyun.co 10.137.38.86 2 u 468 1024 377 14.374 -4.292 6.377
当所有远程服务器（不是本地服务器）的jitter值都为4000，并且reach和dalay的值是0时，就表示时间同步有问题。可能原因有2个：
1）服务器端的防火墙设置，阻断了123端口（可以用 iptables -t filter -A INPUT -p udp --destination-port 123 -j ACCEPT 解决）
2）每次重启ntp服务器之后，大约3-5分钟客户端才能与服务端建立连接，建立连接之后才能进行时间同步，否则客户端同步时间时会显示
no server suitable for synchronization found的报错信息，不用担心，等会就可以了。
其它主机设置,以node2为例
[root@node2 /]# systemctl stop ntpd.service # 关闭ntp服务
[root@node2 /]# systemctl disable ntpd.service # 禁止开机自启动
[root@node2 ~]# yum install ntpdate -y
[root@node2 ~]# /usr/sbin/ntpdate 192.168.1.101
30 May 17:54:09 ntpdate[20937]: adjust time server 192.168.1.101 offset 0.000758 sec
[root@node2 ~]# crontab –e
*/30 * * * * /usr/sbin/ntpdate 192.168.1.101 > /dev/null 2>&1;/sbin/hwclock -w
[root@node2 ~]# systemctl restart crond.service
[root@node2 ~]# systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: active (running) since 四 2018-05-31 09:05:39 CST; 11s ago
Main PID: 12162 (crond)
CGroup: /system.slice/crond.service
└─12162 /usr/sbin/crond -n
5月 31 09:05:39 node2 systemd[1]: Started Command Scheduler.
5月 31 09:05:39 node2 systemd[1]: Starting Command Scheduler...
7、上传安装包到node1服务器
[root@node1 ~]# mkdir -pv /data/tools
[root@node1 ~]# cd /data/tools
[root@node1 tools]# ll
total 1221212
-rw-r--r-- 1 root root 58688757 May 24 10:23 apache-flume-1.8.0-bin.tar.gz
-rw-r--r-- 1 root root 232229830 May 24 10:25 apache-hive-2.3.3-bin.tar.gz
-rw-r--r-- 1 root root 286104833 May 24 10:26 apache-kylin-2.3.1-hbase1x-bin.tar.gz
-rw-r--r-- 1 root root 216745683 May 24 10:28 hadoop-2.7.6.tar.gz
-rw-r--r-- 1 root root 104659474 May 24 10:27 hbase-1.2.6-bin.tar.gz
-rw-r--r-- 1 root root 47121634 May 24 10:29 hue-3.12.0.tgz
-rw-r--r-- 1 root root 56969154 May 24 10:49 kafka_2.11-1.1.0.tgz
-rw-r--r-- 1 root root 193596110 May 24 10:29 spark-2.1.2-bin-hadoop2.7.tgz
-rw-r--r-- 1 root root 36667596 May 24 10:28 zookeeper-3.4.12.tar.gz
[root@node1 bigdata]#
8、安装JDK
[root@node1 ~]# tar xf /data/tools/jdk-8u162-linux-x64.tar.gz -C /opt/
[root@node1 ~]# [ -L "/opt/java" ] && rm -f /opt/java
[root@node1 ~]# cd /opt/ && ln -s /opt/jdk1.8.0_162 /opt/java
[root@node1 ~]# chown -R root:root /opt/jdk1.8.0_162
[root@node1 ~]# echo -e "# java\nexport JAVA_HOME=/opt/java\nexport PATH=\${PATH}:\${JAVA_HOME}/bin:\${JAVA_HOME}/jre/bin\nexport CLESSPATH=.:\${JAVA_HOME}/lib:\${JAVA_HOME}/jre/lib" > /etc/profile.d/java_version.sh
[root@node1 ~]# source /etc/profile.d/java_version.sh
[root@node1 ~]# java -version
java version "1.8.0_162"
Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)
四、 安装zookeeper
官方文档
1、解压zookeeper
[root@node1 ~]# mkdir -pv /data/bigdata/src
[root@node1 ~]# tar -zxvf /data/tools/zookeeper-3.4.12.tar.gz -C /data/bigdata/src
[root@node1 ~]# ln -s /data/bigdata/src/zookeeper-3.4.12 /data/bigdata/zookeeper
# 添加环境变量
[root@node1 ~]# echo -e "# zookeeper\nexport ZOOKEEPER_HOME=/data/bigdata/zookeeper\nexport PATH=\$ZOOKEEPER_HOME/bin:\$PATH" > /etc/profile.d/bigdata_path.sh
[root@node1 ~]# cat /etc/profile.d/bigdata_path.sh
# zookeeper
export ZOOKEEPER_HOME=/data/bigdata/zookeeper
export PATH=$ZOOKEEPER_HOME/bin:$PATH
[root@node1 ~]#
2、配置zoo.cfg文件
[root@node1 ~]# cd /data/bigdata/zookeeper/conf/ #进入conf目录
[root@node1 conf]# cp zoo_sample.cfg zoo.cfg #拷贝模板
[root@node1 conf]# vim zoo.cfg
# The number of millinode2s of each tick
tickTime=2000
# The number of ticks that the initial
# synchronization phase can take
initLimit=10
# The number of ticks that can pass between
# sending a request and getting an acknowledgement
syncLimit=5
# the directory where the snapshot is stored.
# do not use /tmp for storage, /tmp here is just
# example sakes.
dataDir=/data/bigdata/zookeeper/data # 添加
dataLogDir=/data/bigdata/zookeeper/dataLog # 添加
# the port at which the clients will connect
clientPort=2181
# the maximum number of client connections.
# increase this if you need to handle more clients
#maxClientCnxns=60
#
# Be sure to read the maintenance section of the
# administrator guide before turning on autopurge.
#
# http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance
#
# The number of snapshots to retain in dataDir
#autopurge.snapRetainCount=3
# Purge task interval in hours
# Set to "0" to disable auto purge feature
#autopurge.purgeInterval=1
server.1=node1:2888:3888 # 添加
server.2=node2:2888:3888
server.3=node3:2888:3888
3、添加myid，分发(安装个数为奇数)
# 创建指定目录：dataDir目录下增加myid文件;myid中写当前zookeeper服务的id, 因为server.1=node1:2888:3888 server指定的是1,
[root@node1 conf]# mkdir -pv /data/bigdata/zookeeper/{data,dataLog}
[root@node1 conf]# echo 1 > /data/bigdata/zookeeper/data/myid
4、分发：
[root@node2 ~]# mkdir -pv /data/bigdata/
[root@node3 ~]# mkdir -pv /data/bigdata/
[root@node1 conf]# scp -rp /data/bigdata/src node2:/data/bigdata/
[root@node1 conf]# scp -rp /data/bigdata/src node3:/data/bigdata/
[root@node2 ~]# ln -s /data/bigdata/src/zookeeper-3.4.12 /data/bigdata/zookeeper
[root@node3 ~]# ln -s /data/bigdata/src/zookeeper-3.4.12 /data/bigdata/zookeeper
# 在其余机子配置，node2下面的myid是2，node3下面myid是3，这些都是根据server来的
[root@node2 ~]# echo 2 > /data/bigdata/zookeeper/data/myid
[root@node3 ~]# echo 3 > /data/bigdata/zookeeper/data/myid
五、 安装Hadoop
官方文档
- 生产环境：两个主节点只装namenode，不装datanode；
1、解压hadoop
[root@node1 ~]# tar -zxvf /data/tools/hadoop-2.7.6.tar.gz -C /data/bigdata/src
[root@node1 ~]# ln -s /data/bigdata/src/hadoop-2.7.6 /data/bigdata/hadoop
# 添加环境变量
[root@node1 ~]# echo -e "\n# hadoop\nexport HADOOP_HOME=/data/bigdata/hadoop\nexport PATH=\$HADOOP_HOME/bin:\$HADOOP_HOME/sbin\$PATH" >> /etc/profile.d/bigdata_path.sh
[root@node1 ~]# cat /etc/profile.d/bigdata_path.sh
# zookeeper
export ZOOKEEPER_HOME=/data/bigdata/zookeeper
export PATH=$ZOOKEEPER_HOME/bin:$PATH
# hadoop
export HADOOP_HOME=/data/bigdata/hadoop
export PATH=$HADOOP_HOME/bin:$HADOOP_HOME/sbin:$PATH
[root@node1 ~]#
2、配置hadoop-env.sh
[root@node1 ~]# cd /data/bigdata/hadoop/etc/hadoop/
[root@node1 hadoop]# vim hadoop-env.sh
export JAVA_HOME=/opt/java # 添加
export HADOOP_SSH_OPTS="-p 22"
3、配置core-site.xml
[root@node1 hadoop]# vim core-site.xml
<configuration>
<property>
<name>fs.defaultFSname>
<value>hdfs://myclustervalue>
property>
<property>
<name>hadoop.tmp.dirname>
<value>/data/bigdata/tmpvalue>
property>
<property>
<name>ha.zookeeper.quorumname>
<value>node1:2181,node2:2181,node3:2181value>
<discription>zookeeper客户端连接地址discription>
property>
<property>
<name>ha.zookeeper.session-timeout.msname>
<value>10000value>
property>
<property>
<name>fs.trash.intervalname>
<value>1440value>
<discription>以分钟为单位的垃圾回收时间，垃圾站中数据超过此时间，会被删除。如果是0，垃圾回收机制关闭。discription>
property>
<property>
<name>fs.trash.checkpoint.intervalname>
<value>1440value>
<discription>以分钟为单位的垃圾回收检查间隔。discription>
property>
<property>
<name>hadoop.security.authenticationname>
<value>simplevalue>
<discription>可以设置的值为 simple (无认证) 或者 kerberos（一种安全认证系统）discription>
property>
<property>
<name>hadoop.proxyuser.hue.hostsname>
<value>*value>
property>
<property>
<name>hadoop.proxyuser.hue.groupsname>
<value>*value>
property>
<property>
<name>hadoop.proxyuser.root.hostsname>
<value>*value>
property>
<property>
<name>hadoop.proxyuser.root.groupsname>
<value>*value>
property>
configuration>
新建指定目录
[root@node1 hadoop]# mkdir -p /data/bigdata/tmp
4、配置yarn-site.xml
[root@node1 hadoop]# vim yarn-site.xml
<configuration>
<property>
<name>yarn.app.mapreduce.am.scheduler.connection.wait.interval-msname>
<value>5000value>
<discription>schelduler失联等待连接时间discription>
property>
<property>
<name>yarn.nodemanager.aux-servicesname>
<value>mapreduce_shufflevalue>
<discription>NodeManager上运行的附属服务。需配置成mapreduce_shuffle，才可运行MapReduce程序discription>
property>
<property>
<name>yarn.resourcemanager.connect.retry-interval.msname>
<value>5000value>
<description>How often to try connecting to the ResourceManager.description>
property>
<property>
<name>yarn.resourcemanager.ha.enabledname>
<value>truevalue>
<discription>是否启用RM HA，默认为false（不启用）discription>
property>
<property>
<name>yarn.resourcemanager.ha.automatic-failover.enabledname>
<value>truevalue>
<discription>是否启用自动故障转移。默认情况下，在启用HA时，启用自动故障转移。discription>
property>
<property>
<name>yarn.resourcemanager.ha.automatic-failover.embeddedname>
<value>truevalue>
<discription>启用内置的自动故障转移。默认情况下，在启用HA时，启用内置的自动故障转移。discription>
property>
<property>
<name>yarn.resourcemanager.cluster-idname>
<value>cluster1value>
<discription>集群的Id，elector使用该值确保RM不会做为其它集群的active。discription>
property>
<property>
<name>yarn.resourcemanager.ha.rm-idsname>
<value>rm1,rm2value>
<discription>RMs的逻辑id列表,rm管理资源器；一般配两个，一个起作用 其他备用；用逗号分隔,如:rm1,rm2 discription>
property>
<property>
<name>yarn.resourcemanager.hostname.rm1name>
<value>node3value>
<discription>RM的hostnamediscription>
property>
<property>
<name>yarn.resourcemanager.scheduler.address.rm1name>
<value>${yarn.resourcemanager.hostname.rm1}:8030value>
<discription>RM对AM暴露的地址,AM通过地址想RM申请资源,释放资源等discription>
property>
<property>
<name>yarn.resourcemanager.resource-tracker.address.rm1name>
<value>${yarn.resourcemanager.hostname.rm1}:8031value>
<discription>RM对NM暴露地址,NM通过该地址向RM汇报心跳,领取任务等discription>
property>
<property>
<name>yarn.resourcemanager.address.rm1name>
<value>${yarn.resourcemanager.hostname.rm1}:8032value>
<discription>RM对客户端暴露的地址,客户端通过该地址向RM提交应用程序等discription>
property>
<property>
<name>yarn.resourcemanager.admin.address.rm1name>
<value>${yarn.resourcemanager.hostname.rm1}:8033value>
<discription>RM对管理员暴露的地址.管理员通过该地址向RM发送管理命令等discription>
property>
<property>
<name>yarn.resourcemanager.webapp.address.rm1name>
<value>${yarn.resourcemanager.hostname.rm1}:8088value>
<discription>RM对外暴露的web http地址，用户可通过该地址在浏览器中查看集群信息discription>
property>
<property>
<description>The https adddress of the RM web application.description>
<name>yarn.resourcemanager.webapp.https.address.rm1name>
<value>${yarn.resourcemanager.hostname.rm1}:8090value>
property>
<property>
<name>yarn.resourcemanager.hostname.rm2name>
<value>node4value>
property>
<property>
<name>yarn.resourcemanager.scheduler.address.rm2name>
<value>${yarn.resourcemanager.hostname.rm2}:8030value>
property>
<property>
<name>yarn.resourcemanager.resource-tracker.address.rm2name>
<value>${yarn.resourcemanager.hostname.rm2}:8031value>
property>
<property>
<name>yarn.resourcemanager.address.rm2name>
<value>${yarn.resourcemanager.hostname.rm2}:8032value>
property>
<property>
<name>yarn.resourcemanager.admin.address.rm2name>
<value>${yarn.resourcemanager.hostname.rm2}:8033value>
property>
<property>
<name>yarn.resourcemanager.webapp.address.rm2name>
<value>${yarn.resourcemanager.hostname.rm2}:8088value>
property>
<property>
<description>The https adddress of the RM web application.description>
<name>yarn.resourcemanager.webapp.https.address.rm2name>
<value>${yarn.resourcemanager.hostname.rm2}:8090value>
property>
<property>
<name>yarn.resourcemanager.recovery.enabledname>
<value>truevalue>
<discription>默认值为false，也就是说resourcemanager挂了相应的正在运行的任务在rm恢复后不能重新启动discription>
property>
<property>
<name>yarn.resourcemanager.store.classname>
<value>org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStorevalue>
<discription>状态存储的类discription>
property>
<property>
<name>ha.zookeeper.quorumname>
<value>node1:2181,node2:2181,node3:2181value>
property>
<property>
<name>yarn.resourcemanager.zk-addressname>
<value>${ha.zookeeper.quorum}value>
<discription>ZooKeeper服务器的地址（主机：端口号），既用于状态存储也用于内嵌的leader-election。discription>
property>
<property>
<name>yarn.nodemanager.addressname>
<value>${yarn.nodemanager.hostname}:8041value>
<discription>The address of the container manager in the NM.discription>
property>
<property>
<name>yarn.nodemanager.resource.memory-mbname>
<value>58000value>
<discription>该节点上nodemanager可使用的物理内存总量discription>
property>
<property>
<name>yarn.nodemanager.resource.cpu-vcoresname>
<value>16value>
<discription>该节点上nodemanager可使用的虚拟CPU个数discription>
property>
<property>
<name>yarn.nodemanager.vmem-pmem-rationame>
<value>2value>
<discription>任务每使用1MB物理内存，最多可使用虚拟内存量，默认是2.1。discription>
property>
<property>
<name>yarn.scheduler.minimum-allocation-mbname>
<value>1024value>
<discription>单个任务可申请的最小物理内存量discription>
property>
<property>
<name>yarn.scheduler.maximum-allocation-mbname>
<value>58000value>
<discription>单个任务可申请的最大物理内存量discription>
property>
<property>
<name>yarn.scheduler.minimum-allocation-vcoresname>
<value>1value>
<discription>单个任务可申请的最小虚拟CPU个数discription>
property>
<property>
<name>yarn.scheduler.maximum-allocation-vcoresname>
<value>16value>
<discription>单个任务可申请的最大虚拟CPU个数discription>
property>
configuration>
5、配置mapred-site.xml
[root@node1 hadoop]# cp mapred-site.xml{.template,}
[root@node1 hadoop]# vim mapred-site.xml
<configuration>
<property>
<name>mapreduce.framework.namename>
<value>yarnvalue>
property>
<property>
<name>mapreduce.jobhistory.addressname>
<value>sjfx:10020value>
property>
configuration>
6、配置hdfs-site.xml
[root@node1 hadoop]# vim hdfs-site.xml
<configuration>
<property>
<name>dfs.permissionsname>
<value>truevalue>
<description>
If "true", enable permission checking in HDFS.
If "false", permission checking is turned off,
but all other behavior is unchanged.
Switching from one parameter value to the other does not change the mode,
owner or group of files or directories.
description>
property>
<property>
<name>dfs.replicationname>
<value>2value>
<description>保存副本数description>
property>
<property>
<discription>持久存储名字空间，事务日志的本地路径discription>
<name>dfs.namenode.name.dirname>
<value>/data/bigdata/hdfs/namevalue>
property>
<property>
<discription>datanode存放数据的路径，单个节点单配，多个目录逗号分隔discription>
<name>dfs.datanode.data.dirname>
<value>/data/bigdata/hdfs/datavalue>
property>
<property>
<discription>指定用于在DataNode间传输block数据的最大线程数discription>
<name>dfs.datanode.max.transfer.threadsname>
<value>16384value>
property>
<property>
<name>dfs.datanode.balance.bandwidthPerSecname>
<value>52428800value>
<description>
Specifies the maximum amount of bandwidth that each datanode
can utilize for the balancing purpose in term of
the number of bytes per second.
description>
property>
<property>
<name>dfs.datanode.balance.max.concurrent.movesname>
<value>50value>
<description>增加DataNode上转移block的Xceiver的个数上限。description>
property>
<property>
<name>dfs.nameservicesname>
<value>myclustervalue>
property>
<property>
<name>dfs.ha.namenodes.myclustername>
<value>nn1,nn2value>
property>
<property>
<name>dfs.namenode.rpc-address.mycluster.nn1name>
<value>node1:8020value>
property>
<property>
<name>dfs.namenode.rpc-address.mycluster.nn2name>
<value>node2:8020value>
property>
<property>
<name>dfs.namenode.http-address.mycluster.nn1name>
<value>node1:50070value>
property>
<property>
<name>dfs.namenode.http-address.mycluster.nn2name>
<value>node2:50070value>
property>
<property>
<name>dfs.namenode.journalnodename>
<value>node1:8485;node2:8485;node3:8485value>
<discription>journalnode为了解决hadoop单点故障，给namenode做元数据同步的，奇数个,一般3个或5个discription>
property>
<property>
<name>dfs.namenode.shared.edits.dirname>
<value>qjournal://${dfs.namenode.journalnode}/myclustervalue>
property>
<property>
<name>dfs.client.failover.proxy.provider.myclustername>
<value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvidervalue>
property>
<property>
<name>dfs.ha.fencing.methodsname>
<value>sshfencevalue>
property>
<property>
<name>dfs.ha.fencing.ssh.private-key-filesname>
<value>/root/.ssh/id_dsavalue>
property>
<property>
<name>dfs.journalnode.edits.dirname>
<value>${hadoop.tmp.dir}/dfs/journalvalue>
property>
<property>
<name>dfs.permissions.superusergroupname>
<value>rootvalue>
<description>超级用户组名description>
property>
<property>
<name>dfs.ha.automatic-failover.enabledname>
<value>truevalue>
<description>开启自动故障转移description>
property>
configuration>
新建相应目录
[root@node1 hadoop]# mkdir -pv /data/bigdata/tmp/dfs/journal
7、配置capacity-scheduler.xml
[root@node1 hadoop]# vim capacity-scheduler.xml
<configuration>
<property>
<name>yarn.scheduler.capacity.maximum-applicationsname>
<value>10000value>
<description>
Maximum number of applications that can be pending and running.
description>
property>
<property>
<name>yarn.scheduler.capacity.maximum-am-resource-percentname>
<value>0.1value>
<description>
Maximum percent of resources in the cluster which can be used to run
application masters i.e. controls number of concurrent running
applications.
description>
property>
<property>
<name>yarn.scheduler.capacity.resource-calculatorname>
<value>org.apache.hadoop.yarn.util.resource.DominantResourceCalculatorvalue>
<description>
The ResourceCalculator implementation to be used to compare
Resources in the scheduler.
The default i.e. DefaultResourceCalculator only uses Memory while
DominantResourceCalculator uses dominant-resource to compare
multi-dimensional resources such as Memory, CPU etc.
description>
property>
<property>
<name>yarn.scheduler.capacity.root.queuesname>
<value>defaultvalue>
<description>
The queues at the this level (root is the root queue).
description>
property>
<property>
<name>yarn.scheduler.capacity.root.default.capacityname>
<value>100value>
<description>Default queue target capacity.description>
property>
<property>
<name>yarn.scheduler.capacity.root.default.user-limit-factorname>
<value>1value>
<description>
Default queue user limit a percentage from 0.0 to 1.0.
description>
property>
<property>
<name>yarn.scheduler.capacity.root.default.maximum-capacityname>
<value>100value>
<description>
The maximum capacity of the default queue.
description>
property>
<property>
<name>yarn.scheduler.capacity.root.default.statename>
<value>RUNNINGvalue>
<description>
The state of the default queue. State can be one of RUNNING or STOPPED.
description>
property>
<property>
<name>yarn.scheduler.capacity.root.default.acl_submit_applicationsname>
<value>*value>
<description>
The ACL of who can submit jobs to the default queue.
description>
property>
<property>
<name>yarn.scheduler.capacity.root.default.acl_administer_queuename>
<value>*value>
<description>
The ACL of who can administer jobs on the default queue.
description>
property>
<property>
<name>yarn.scheduler.capacity.node-locality-delayname>
<value>40value>
<description>
Number of missed scheduling opportunities after which the CapacityScheduler
attempts to schedule rack-local containers.
Typically this should be set to number of nodes in the cluster, By default is setting
approximately number of nodes in one rack which is 40.
description>
property>
<property>
<name>yarn.scheduler.capacity.queue-mappingsname>
<value>value>
<description>
A list of mappings that will be used to assign jobs to queues
The syntax for this list is [u|g]:[name]:[queue_name][,next mapping]*
Typically this list will be used to map users to queues,
for example, u:%user:%user maps all users to queues with the same name
as the user.
description>
property>
<property>
<name>yarn.scheduler.capacity.queue-mappings-override.enablename>
<value>falsevalue>
<description>
If a queue mapping is present, will it override the value specified
by the user? This can be used by administrators to place jobs in queues
that are different than the one specified by the user.
The default is false.
description>
property>
configuration>
8、配置slaves
[root@node1 hadoop]# vim slaves
node1
node2
node3
node4
node5
9、修改$HADOOP_HOME/sbin/hadoop-daemon.sh
[root@node1 hadoop]# cd /data/bigdata/hadoop/sbin/
[root@node1 sbin]# vim hadoop-daemon.sh
#添加：
HADOOP_PID_DIR=/data/bigdata/hdfs/pids
YARN_PID_DIR=/data/bigdata/hdfs/pids
# 新建相应目录
[root@node1 sbin]# mkdir -pv /data/bigdata/hdfs/{name,data,pids}
10、修改$HADOOP_HOME/sbin/yarn-daemon.sh
#添加：
[root@node1 sbin]# vim yarn-daemon.sh
HADOOP_PID_DIR=/data/bigdata/hdfs/pids
YARN_PID_DIR=/data/bigdata/hdfs/pids
11、分发
[root@node1 sbin]# scp -rp /data/bigdata/src/hadoop-2.7.6 node2:/data/bigdata/src/
[root@node1 sbin]# scp -rp /data/bigdata/src/hadoop-2.7.6 node3:/data/bigdata/src/
[root@node1 sbin]# scp -rp /data/bigdata/src/hadoop-2.7.6 node4:/data/bigdata/src/
[root@node1 sbin]# scp -rp /data/bigdata/src/hadoop-2.7.6 node5:/data/bigdata/src/
[root@node2 ~]# ln -s /data/bigdata/src/hadoop-2.7.6 /data/bigdata/hadoop
[root@node3 ~]# ln -s /data/bigdata/src/hadoop-2.7.6 /data/bigdata/hadoop
[root@node4 ~]# ln -s /data/bigdata/src/hadoop-2.7.6 /data/bigdata/hadoop
[root@node5 ~]# ln -s /data/bigdata/src/hadoop-2.7.6 /data/bigdata/hadoop
六、启动过程
1、启动zookeeper服务:下面两种方法选一
(1) 同时开启所有zookeeper节点
# node1节点
[root@node1 ~]# cd /data/bigdata/zookeeper/bin
[root@node1 conf]# zkServer.sh start
# node2节点
[root@node2 ~]# cd /data/bigdata/zookeeper/bin
[root@node2 conf]# zkServer.sh start
# node3节点
[root@node3 ~]# cd /data/bigdata/zookeeper/bin
[root@node3 conf]# zkServer.sh start
# 相应进程(其它类似)
[root@node1 ~]# jps
23993 QuorumPeerMain
24063 Jps
[root@node1 ~]#
(2) 集群启动
由于zookeeper没有提供同时启动集群中所有节点的执行脚本，在生产中逐个节点启动稍微有些麻烦，自定义一个脚本用来启动集群中所有节点，如下：
[root@node1 bigdata]# cat zookeeper_all_op.sh
#!/bin/bash
# start zookeeper
zookeeperHome=/data/bigdata/src/zookeeper-3.4.12
zookeeperArr=( "node1" "node2" "node3" )
for znode in ${zookeeperArr[@]}; do
ssh -p 22 -q root@$znode \
"
export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
source /etc/profile
$zookeeperHome/bin/zkServer.sh $1
"
echo "$znode zookeeper $1 done"
done
# 启动
[root@node1 bigdata]# ./zookeeper_all_op.sh start
# 查看： leader为领导者（一台）， follower为追随者；
[root@node1 bigdata]# ./zookeeper_all_op.sh status
ZooKeeper JMX enabled by default
Using config: /data/bigdata/src/zookeeper-3.4.12/bin/../conf/zoo.cfg
Mode: follower
node1 zookeeper status done
ZooKeeper JMX enabled by default
Using config: /data/bigdata/src/zookeeper-3.4.12/bin/../conf/zoo.cfg
Mode: leader
node2 zookeeper status done
ZooKeeper JMX enabled by default
Using config: /data/bigdata/src/zookeeper-3.4.12/bin/../conf/zoo.cfg
Mode: follower
node3 zookeeper status done
[root@node1 bigdata]#
(3) 启动客户端脚本
[root@node1 bigdata]# ./zookeeper/bin/zkCli.sh -server node2:2181
Connecting to node2:2181
2018-06-13 17:28:21,115 [myid:] - INFO [main:Environment@100] - Client environment:zookeeper.version=3.4.12-e5259e437540f349646870ea94dc2658c4e44b3b, built on 03/27/2018 03:55 GMT
2018-06-13 17:28:21,119 [myid:] - INFO [main:Environment@100] - Client environment:host.name=node1
......
省略
......
2018-06-13 17:28:21,220 [myid:] - INFO [main-SendThread(node2:2181):ClientCnxn$SendThread@878] - Socket connection established to node2/192.168.1.102:2181, initiating session
2018-06-13 17:28:21,229 [myid:] - INFO [main-SendThread(node2:2181):ClientCnxn$SendThread@1302] - Session establishment complete on server node2/192.168.1.102:2181, sessionid = 0x20034776a7c000e, negotiated timeout = 30000
WATCHER::
WatchedEvent state:SyncConnected type:None path:null
[zk: node2:2181(CONNECTED) 0] help
ZooKeeper -server host:port cmd args
stat path [watch]
set path data [version]
ls path [watch]
delquota [-n|-b] path
ls2 path [watch]
setAcl path acl
setquota -n|-b val path
history
redo cmdno
printwatches on|off
delete path [version]
sync path
listquota path
rmr path
get path [watch]
create [-s] [-e] path data acl
addauth scheme auth
quit
getAcl path
close
connect host:port
[zk: node2:2181(CONNECTED) 1] quit
Quitting...
2018-06-13 17:28:37,984 [myid:] - INFO [main:ZooKeeper@687] - Session: 0x20034776a7c000e closed
2018-06-13 17:28:37,986 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@521] - EventThread shut down for session: 0x20034776a7c000e
[root@node1 bigdata]#
2、启动所有journalnode节点
# node1节点
[root@node1 ~]# cd /data/bigdata/hadoop/
[root@node1 hadoop]# ./sbin/hadoop-daemon.sh start journalnode
starting journalnode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-journalnode-node1.out
# 相应进程(其它类似)
[root@node1 ~]# jps
23993 QuorumPeerMain
24474 JournalNode # 新启动的进程
24910 Jps
[root@node1 ~]#
# journalnode我配了3个
# node2节点
[root@node2 ~]# cd /data/bigdata/hadoop/
[root@node2 hadoop]# ./sbin/hadoop-daemon.sh start journalnode
# node3节点
[root@node3 ~]# cd /data/bigdata/hadoop/
[root@node3 hadoop]# ./sbin/hadoop-daemon.sh start journalnode
3、格式化namenode目录(主节点node1)
[root@node1 hadoop]# cd /data/bigdata/hadoop
[root@node1 hadoop]# ./bin/hdfs namenode -format
18/06/04 14:24:03 INFO namenode.NameNode: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host = node1/192.168.1.101
STARTUP_MSG: args = [-format]
STARTUP_MSG: version = 2.7.6
..........................................
省略若干
...........................................
18/06/04 14:24:05 INFO namenode.NNStorageRetentionManager: Going to retain 1 images with txid >= 0
18/06/04 14:24:05 INFO util.ExitUtil: Exiting with status 0
18/06/04 14:24:05 INFO namenode.NameNode: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at node1/192.168.1.101
************************************************************/
[root@node1 hadoop]#
4、启动当前格式化的namenode进程(主节点node1)
[root@node1 hadoop]# ./sbin/hadoop-daemon.sh start namenode
starting namenode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-namenode-node1.out
[root@node1 ~]# jps # # 相应进程
25155 Jps
23993 QuorumPeerMain
25050 NameNode # name节点
24474 JournalNode
[root@node1 ~]#
5、在没有格式化的NN上 执行同步命令(副节点node2)
[root@node2 hadoop]# ./bin/hdfs namenode -bootstrapStandby
18/06/04 14:26:55 INFO namenode.NameNode: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host = node2/192.168.1.102
STARTUP_MSG: args = [-bootstrapStandby]
STARTUP_MSG: version = 2.7.6
..........................................
省略若干
...........................................
************************************************************/
18/06/04 14:26:55 INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT]
18/06/04 14:26:55 INFO namenode.NameNode: createNameNode [-bootstrapStandby]
18/06/04 14:26:55 WARN common.Util: Path /data/bigdata/hdfs/name should be specified as a URI in configuration files. Please update hdfs configuration.
18/06/04 14:26:55 WARN common.Util: Path /data/bigdata/hdfs/name should be specified as a URI in configuration files. Please update hdfs configuration.
=====================================================
About to bootstrap Standby ID nn2 from:
Nameservice ID: mycluster
Other Namenode ID: nn1
Other NN's HTTP address: http://node1:50070
Other NN's IPC address: node1/192.168.1.101:8020
Namespace ID: 736429223
Block pool ID: BP-1022667957-192.168.1.101-1528093445721
Cluster ID: CID-9d4854cd-7201-4e0d-9536-36e73195dc5a
Layout version: -63
isUpgradeFinalized: true
=====================================================
18/06/04 14:26:56 INFO common.Storage: Storage directory /data/bigdata/hdfs/name has been successfully formatted.
18/06/04 14:26:56 WARN common.Util: Path /data/bigdata/hdfs/name should be specified as a URI in configuration files. Please update hdfs configuration.
18/06/04 14:26:56 WARN common.Util: Path /data/bigdata/hdfs/name should be specified as a URI in configuration files. Please update hdfs configuration.
18/06/04 14:26:57 INFO namenode.TransferFsImage: Opening connection to http://node1:50070/imagetransfer?getimage=1&txid=0&storageInfo=-63:736429223:0:CID-9d4854cd-7201-4e0d-9536-36e73195dc5a
18/06/04 14:26:57 INFO namenode.TransferFsImage: Image Transfer timeout configured to 60000 milliseconds
18/06/04 14:26:57 INFO namenode.TransferFsImage: Transfer took 0.00s at 0.00 KB/s
18/06/04 14:26:57 INFO namenode.TransferFsImage: Downloaded file fsimage.ckpt_0000000000000000000 size 306 bytes.
18/06/04 14:26:57 INFO util.ExitUtil: Exiting with status 0
18/06/04 14:26:57 INFO namenode.NameNode: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at node2/192.168.1.102
************************************************************/
# 如果不成功，直接把node1节点的/data/bigdata/hdfs/name目录复制过来，即可
# 启动从节点
[root@node2 hadoop]# ./sbin/hadoop-daemon.sh start namenode
starting namenode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-namenode-node2.out
6、格式化ZKFC
格式化zkfc,让在zookeeper中生成ha节点，在master上执行如下命令，完成格式化：
[root@node1 hadoop]# ./bin/hdfs zkfc -formatZK
18/06/04 16:53:15 INFO tools.DFSZKFailoverController: Failover controller configured for NameNode NameNode at node1/192.168.1.101:8020
18/06/04 16:53:16 INFO zookeeper.ZooKeeper: Client environment:zookeeper.version=3.4.6-1569965, built on 02/20/2014 09:09 GMT
18/06/04 16:53:16 INFO zookeeper.ZooKeeper: Client environment:host.name=node1
18/06/04 16:53:16 INFO zookeeper.ZooKeeper: Client environment:java.version=1.8.0_162
18/06/04 16:53:16 INFO zookeeper.ZooKeeper: Client environment:java.vendor=Oracle Corporation
18/06/04 16:53:16 INFO zookeeper.ZooKeeper: Client environment:java.home=/opt/jdk1.8.0_162/jre
..........................................
省略若干
...........................................
18/06/04 16:53:16 INFO ha.ActiveStandbyElector: Session connected.
18/06/04 16:53:16 INFO ha.ActiveStandbyElector: Successfully created /hadoop-ha/mycluster in ZK.
18/06/04 16:53:16 INFO zookeeper.ZooKeeper: Session: 0x20034776a7c0000 closed
18/06/04 16:53:16 INFO zookeeper.ClientCnxn: EventThread shut down
[root@node1 hadoop]# ./sbin/hadoop-daemon.sh start zkfc
starting zkfc, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-zkfc-node1.out
[root@node1 hadoop]# jps
5443 DFSZKFailoverController # 新进程
4664 JournalNode
23993 QuorumPeerMain
5545 Jps
4988 NameNode
[root@node1 hadoop]#
# 另一个节点启动zkfc，有namenode运行的节点，都要启动ZKFC
[root@node2 hadoop]# ./sbin/hadoop-daemon.sh start zkfc
7、启动hdfs（datanode）
[root@node1 hadoop]# ./sbin/start-dfs.sh
Starting namenodes on [node1 node2]
node1: namenode running as process 25050. Stop it first.
node2: namenode running as process 30976. Stop it first.
node1: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node1.out
node2: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node2.out
node5: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node5.out
node3: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node3.out
node4: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node4.out
Starting journal nodes [node1 node2 node3]
node1: journalnode running as process 24474. Stop it first.
node3: journalnode running as process 19893. Stop it first.
node2: journalnode running as process 29871. Stop it first.
Starting ZK Failover Controllers on NN hosts [node1 node2]
node1: starting zkfc, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-zkfc-node1.out
node2: starting zkfc, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-zkfc-node2.out
[root@node1 hadoop]# jps
25968 DataNode # 所有节点都有
23993 QuorumPeerMain
5443 DFSZKFailoverController
25050 NameNode
24474 JournalNode
26525 Jps
[root@node1 hadoop]#
8、启动yarn：
[root@node1 hadoop]# ./sbin/start-yarn.sh
starting yarn daemons
starting resourcemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-resourcemanager-node1.out
node1: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node1.out
node2: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node2.out
node4: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node4.out
node3: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node3.out
node5: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node5.out
[root@node1 hadoop]# jps
25968 DataNode
23993 QuorumPeerMain
5443 DFSZKFailoverController
25050 NameNode
24474 JournalNode
27068 Jps
26894 NodeManager # 所有节点都有
[root@node1 hadoop]#
9、两台resourcemanager上启动resourcemanager
（1）单独启动
[root@node3 hadoop]# ./sbin/yarn-daemon.sh start resourcemanager
starting resourcemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-resourcemanager-node3.out
[root@node4 hadoop]# ./sbin/yarn-daemon.sh start resourcemanager
# 相应进程(其它类似)
[root@node3 ~]# jps
21088 NodeManager
21297 ResourceManager # 此进程
19459 QuorumPeerMain
19893 JournalNode
20714 DataNode
21535 Jps
[root@node3 ~]#
（2）集群启动
生产中一个hdfs集群会有两个ResourceManager节点，若逐个节点启动稍微有些麻烦，自定义一个脚本用来启动集群中所有ResourceManager节点，如下：
[root@node1 bigdata]# pwd
/data/bigdata
[root@node1 bigdata]# cat yarn_all_resourcemanager.sh
#!/bin/bash
# resourcemanager management
hadoop_yarn_daemon_home=/data/bigdata/hadoop/sbin/
yarn_resourcemanager_node=( "node3" "node4" )
for renode in ${yarn_resourcemanager_node[@]}; do
ssh -p 22 -q root@$znode "
export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
source /etc/profile
cd $hadoop_yarn_daemon_home/ && ./yarn-daemon.sh $1 resourcemanager
"
echo "$renode resourcemanager $1 done"
done
[root@node1 bigdata]#
HDFS和yarn的web控制台默认监听端口分别为50070和8088。可以通过浏览放访问查看运行情况。
例：
http://192.168.1.101:50070/
http://192.168.1.103:8088/
# 停止命令：不操作
$HADOOP_HOME/sbin/stop-dfs.sh
$HADOOP_HOME/sbin/stop-yarn.sh
# 如果一切正常，使用jps可以查看到正在运行的Hadoop服务，机器上的显示结果为：
[root@node1 hadoop]# jps
7312 Jps
1793 NameNode
2163 JournalNode
357 NodeManager
2696 QuorumPeerMain
14428 DFSZKFailoverController
1917 DataNode
到目前为止所启动的进程：
| \ | node1 | node2 | node3 | node4 | node5 |
|---|---|---|---|---|---|
| JDK | ✔ | ✔ | ✔ | ✔ | ✔ |
| QuorumPeerMain | ✔ | ✔ | ✔ | ||
| JournalNode | ✔ | ✔ | ✔ | ||
| NameNode | ✔ | ✔ | |||
| DFSZKFailoverController | ✔ | ✔ | |||
| DataNode | ✔ | ✔ | ✔ | ✔ | ✔ |
| NodeManager | ✔ | ✔ | ✔ | ✔ | ✔ |
| ResourceManager | ✔ | ✔ |
10、验证HDFS的HA功能
在任意一台namenode机器上通过jps命令查找到namenode的进程号，然后通过kill -9的方式杀掉进程，观察另一个namenode节点是否会从状态standby变成active状态。
[root@node1 bigdata]# jps
16704 JournalNode
16288 NameNode
16433 DataNode
23993 QuorumPeerMain
17241 NodeManager
18621 Jps
16942 DFSZKFailoverController
[root@node1 bigdata]# kill -9 16288
然后观察原来是standby状态的namenode机器的zkfc日志，若最后一行出现如下日志，则表示切换成功：
2018-05-31 16:14:41,114 INFOorg.apache.hadoop.ha.ZKFailoverController: Successfully transitioned NameNodeat hd0/192.168.1.102:53310 to active state
这时再通过命令启动被kill掉的namenode进程
[root@node1 bigdata]# ./sbin/hadoop-daemon.sh start namenode
对应进程的zkfc最后一行日志如下：
2018-05-31 16:14:55,683 INFOorg.apache.hadoop.ha.ZKFailoverController: Successfully transitioned NameNodeat hd2/192.168.1.101:53310 to standby state
可以在两台namenode机器之间来回kill掉namenode进程以检查HDFS的HA配置！
七、scala
1、配置前准备
scala运行在jvm虚拟机，需要配置jdk；
2、解压
[root@node1 sbin]# tar -zxvf /data/tools/scala-2.11.12.tgz -C /data/bigdata/src
[root@node1 sbin]# ln -s /data/bigdata/src/scala-2.11.12 /data/bigdata/scala
# 添加环境变量
[root@node1 ~]# echo -e "\n# scala\nexport scala_HOME=/data/bigdata/scala\nexport PATH=\$scala_HOME/bin:\$PATH" >> /etc/profile.d/bigdata_path.sh
[root@node1 ~]# cat /etc/profile.d/bigdata_path.sh
# zookeeper
export ZOOKEEPER_HOME=/data/bigdata/zookeeper
export PATH=$ZOOKEEPER_HOME/bin:$PATH
# hadoop
export HADOOP_HOME=/data/bigdata/hadoop
export PATH=$HADOOP_HOME/bin:$HADOOP_HOME/sbin:$PATH
# scala
export scala_HOME=/data/bigdata/scala
export PATH=$scala_HOME/bin:$PATH
[root@node1 ~]# source /etc/profile
3、查看scala版本
[root@node1 ~]# scala -version
Scala code runner version 2.11.12 -- Copyright 2002-2016, LAMP/EPFL
4、运行scala命令
[root@node1 ~]# scala
Welcome to Scala 2.11.12 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_162).
Type in expressions for evaluation. Or try :help.
scala> 1+1
res0: Int = 2
scala>
如果以上两步没问题，表示scala已安装和配置成功。
八、 安装spark
官方文档
1、解压spark
[root@node1 conf]# tar -zxvf /data/tools/spark-2.1.2-bin-hadoop2.7.tgz -C /data/bigdata/src/
[root@node1 conf]# ln -s /data/bigdata/src/spark-2.1.2-bin-hadoop2.7 /data/bigdata/spark
# 添加环境变量
[root@node1 ~]# echo -e "\n# spark\nexport SPARK_HOME=/data/bigdata/spark\nexport PATH=\$SPARK_HOME/bin:\$PATH" >> /etc/profile.d/bigdata_path.sh
[root@node1 ~]# cat /etc/profile.d/bigdata_path.sh
# zookeeper
export ZOOKEEPER_HOME=/data/bigdata/zookeeper
export PATH=$ZOOKEEPER_HOME/bin:$PATH
# hadoop
export HADOOP_HOME=/data/bigdata/hadoop
export PATH=$HADOOP_HOME/bin:$HADOOP_HOME/sbin:$PATH
# scala
export scala_HOME=/data/bigdata/scala
export PATH=$scala_HOME/bin:$PATH
[root@node1 ~]# source /etc/profile
# spark
export SPARK_HOME=/data/bigdata/spark
export PATH=$SPARK_HOME/bin:$PATH
[root@node1 ~]#
2、配置spark-env.sh
[root@node1 conf]# cd /data/bigdata/spark/conf/
[root@node1 conf]# cp spark-env.sh{.template,}
# 添加：
[root@node1 conf]# vim spark-env.sh
export SPARK_LOCAL_IP="192.168.1.101" # 从节点改为自己的IP（或127.0.0.1 ），或者注掉
export SPARK_MASTER_IP="192.168.1.101"
export JAVA_HOME=/opt/java
export SPARK_PID_DIR=/data/bigdata/hdfs/pids
export SPARK_LOCAL_DIRS= /data/bigdata/sparktmp
export PYSPARK_PYTHON=/usr/local/bin/python3 # 当用python3开发时，配上python3的绝对路径。
# 设置内存，本节点可以调用的内存
export SPARK_WORKER_MEMORY=58g
export SPARK_MASTER_PORT=7077
export HADOOP_CONF_DIR=$HADOOP_HOME/etc/hadoop
export LD_LIBRARY_PATH=$HADOOP_HOME/lib/native
export SPARK_HISTORY_OPTS="-Dspark.history.ui.port=18080 -Dspark.history.retainedApplications=3 -Dspark.history.fs.logDirectory=hdfs://mycluster/directory"
# 限制程序申请资源最大核数，本节点可以调用的cpu核数
export SPARK_MASTER_OPTS="-Dspark.deploy.defaultCores=16"
export SPARK_SSH_OPTS="-p 22 -o StrictHostKeyChecking=no $SPARK_SSH_OPTS"
3、配置spark-defaults.conf
[root@node1 conf]# cp spark-defaults.conf{.template,}
[root@node1 conf]# vim spark-defaults.conf
#添加
spark.serializer org.apache.spark.serializer.KryoSerializer
spark.eventLog.enabled true
spark.eventLog.dir hdfs://mycluster/directory
# 使用Python3+开发时配置；
park.executorEnv.PYTHONHASHSEED=0
# 新建对应目录
[root@node1 conf]# mkdir -pv /data/bigdata/sparktmp
[root@node1 conf]# hdfs dfs -mkdir /directory
说明：spark.executorEnv.PYTHONHASHSEED=0配置：
如果你使用的是Python3+，并且在Spark集群上使用distinct()，reduceByKey()，和join()这几个函数时，就会触发下面的异常：
Exception: Randomness of hash of string should be disabled via PYTHONHASHSEED
python创建遍历对象对象时会对每个对象进行随机哈希创建索引。然而在一个集群上，每个节点计算时对某一个变量创建的索引值不同，会导致数据索引冲突。因此需要设置PYTHONHASHSEED来固定随机种子，保证索引一致。参见：
Spark集群配置（4）：其他填坑杂项
4、配置slaves
[root@node1 conf]# cp slaves{.template,}
[root@node1 conf]# vim slaves
node1
node2
node3
node4
node5
5、分发
[root@node1 conf]# scp -rp /data/bigdata/src/spark-2.1.2-bin-hadoop2.7 node2:/data/bigdata/src/
[root@node1 conf]# scp -rp /data/bigdata/src/spark-2.1.2-bin-hadoop2.7 node3:/data/bigdata/src/
[root@node1 conf]# scp -rp /data/bigdata/src/spark-2.1.2-bin-hadoop2.7 node4:/data/bigdata/src/
[root@node1 conf]# scp -rp /data/bigdata/src/spark-2.1.2-bin-hadoop2.7 node5:/data/bigdata/src/
# 分发创建的目录
[root@node1 bigdata]# scp -rp /data/bigdata/{hdfs,sparktmp,tmp} node2:/data/bigdata/
[root@node1 bigdata]# scp -rp /data/bigdata/{hdfs,sparktmp,tmp} node3:/data/bigdata/
[root@node1 bigdata]# scp -rp /data/bigdata/{hdfs,sparktmp,tmp} node4:/data/bigdata/
[root@node1 bigdata]# scp -rp /data/bigdata/{hdfs,sparktmp,tmp} node5:/data/bigdata/
# 创建软连接
[root@node2 ~]# ln -s /data/bigdata/src/spark-2.1.2-bin-hadoop2.7 /data/bigdata/spark
[root@node3 ~]# ln -s /data/bigdata/src/spark-2.1.2-bin-hadoop2.7 /data/bigdata/spark
[root@node4 ~]# ln -s /data/bigdata/src/spark-2.1.2-bin-hadoop2.7 /data/bigdata/spark
[root@node5 ~]# ln -s /data/bigdata/src/spark-2.1.2-bin-hadoop2.7 /data/bigdata/spark
# 修改$SPARK_HOME/conf/spark-env.sh中的SPARK_LOCAL_IP参数
[root@node2 ~]# vim $SPARK_HOME/conf/spark-env.sh
export SPARK_LOCAL_IP="192.168.1.102"
[root@node3 ~]# vim $SPARK_HOME/conf/spark-env.sh
export SPARK_LOCAL_IP="192.168.1.103"
[root@node4 ~]# vim $SPARK_HOME/conf/spark-env.sh
export SPARK_LOCAL_IP="192.168.1.104"
[root@node5 ~]# vim $SPARK_HOME/conf/spark-env.sh
export SPARK_LOCAL_IP="192.168.1.105"
6、启动spark
[root@node1 bin]# cd /data/bigdata/spark/sbin
[root@node1 sbin]# ./start-all.sh
starting org.apache.spark.deploy.master.Master, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.master.Master-1-node1.out
node1: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node1.out
node5: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node5.out
node3: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node3.out
node4: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node4.out
node2: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node2.out
[root@node1 sbin]# jps
5443 DFSZKFailoverController
5684 Master # spark的master
1092 HRegionServer
5846 Worker # spark进程
904 HMaster
4664 JournalNode
23993 QuorumPeerMain
6266 Jps
7227 NodeManager
4988 NameNode
6495 DataNode
web界面：http://192.168.1.101:8080/
[root@node1 sbin]# ./start-history-server.sh
starting org.apache.spark.deploy.history.HistoryServer, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.history.HistoryServer-1-node1.out
[root@node1 sbin]# jps
5443 DFSZKFailoverController
5684 Master # spark的master
1092 HRegionServer
5846 Worker # spark进程
904 HMaster
4664 JournalNode
29366 HistoryServer # spark 保存历史日志记录的
23993 QuorumPeerMain
6266 Jps
7227 NodeManager
4988 NameNode
6495 DataNode
访问WEBUI： http://192.168.1.101:18080/
到目前为止所启动的进程：
| \ | node1 | node2 | node3 | node4 | node5 |
|---|---|---|---|---|---|
| JDK | ✔ | ✔ | ✔ | ✔ | ✔ |
| QuorumPeerMain | ✔ | ✔ | ✔ | ||
| JournalNode | ✔ | ✔ | ✔ | ||
| NameNode | ✔ | ✔ | |||
| DFSZKFailoverController | ✔ | ✔ | |||
| DataNode | ✔ | ✔ | ✔ | ✔ | ✔ |
| NodeManager | ✔ | ✔ | ✔ | ✔ | ✔ |
| ResourceManager | ✔ | ✔ | |||
| Master | ✔ | ||||
| Worker | ✔ | ✔ | ✔ | ✔ | ✔ |
| HistoryServer | ✔ |
九、 安装hbase
Master和Hadoop的NameNode进程运行在同一台主机上，与DataNode通信
以读写HDFS的数据。RegionServer跟Hadoop的DataNode运行在同一台主机上。
参考：
官方文档
hbase 数据库简介安装与常用命令的使用
1、解压hbase
[root@node1 sbin]# tar -zxvf /data/tools/hbase-1.2.6-bin.tar.gz -C /data/bigdata/src
[root@node1 sbin]# ln -s /data/bigdata/src/hbase-1.2.6 /data/bigdata/hbase
# 添加环境变量
[root@node1 ~]# echo -e "\n# hbase\nexport HBASE_HOME=/data/bigdata/hbase\nexport PATH=\$HBASE_HOME/bin:\$PATH" >> /etc/profile.d/bigdata_path.sh
[root@node1 ~]# cat /etc/profile.d/bigdata_path.sh
# zookeeper
export ZOOKEEPER_HOME=/data/bigdata/zookeeper
export PATH=$ZOOKEEPER_HOME/bin:$PATH
# hadoop
export HADOOP_HOME=/data/bigdata/hadoop
export PATH=$HADOOP_HOME/bin:$HADOOP_HOME/sbin:$PATH
# scala
export scala_HOME=/data/bigdata/scala
export PATH=$scala_HOME/bin:$PATH
# spark
export SPARK_HOME=/data/bigdata/spark
export PATH=$SPARK_HOME/bin:$PATH
# hbase
export HBASE_HOME=/data/bigdata/hbase
export PATH=$HBASE_HOME/bin:$PATH
[root@node1 ~]#
2、修改$HBASE_HOME/conf/hbase-env.sh,添加
[root@node1 sbin]# cd /data/bigdata/hbase/conf
[root@node1 conf]# vim hbase-env.sh
export JAVA_HOME=/opt/java
export HBASE_HOME=/data/bigdata/hbase
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HADOOP_HOME/lib/native/
export HBASE_LIBRARY_PATH=$HBASE_LIBRARY_PATH:$HBASE_HOME/lib/native/
# 设置到Hadoop的etc/hadoop目录是用来引导Hbase找到Hadoop,也就是说hbase和hadoop进行关联【必须设置,否则hmaster起不来】
export HBASE_CLASSPATH=$HADOOP_HOME/etc/hadoop
export HBASE_MANAGES_ZK=false #不启用hbase自带的zookeeper
export HBASE_PID_DIR=/data/bigdata/hdfs/pids
export HBASE_SSH_OPTS="-o ConnectTimeout=1 -p 22" # ssh端口；
# jdk1.8及以上版本注掉下面两行
# Configure PermSize. Only needed in JDK7. You can safely remove it for JDK8+
#export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS -XX:PermSize=128m -XX:MaxPermSize=128m"
#export HBASE_REGIONSERVER_OPTS="$HBASE_REGIONSERVER_OPTS -XX:PermSize=128m -XX:MaxPermSize=128m"
3、修改regionservers文件
[root@node1 conf]# vim regionservers
node1
node2
node3
4、修改hbase-site.xml文件
[root@node1 conf]# vim hbase-site.xml
<configuration>
<property>
<name>hbase.rootdirname>
<value>hdfs://mycluster/hbasevalue>
property>
<property>
<name>hbase.zookeeper.quorumname>
<value>node1,node2,node3value>
<description>指定集群zookeeper主机名description>
property>
<property>
<name>hbase.zookeeper.property.clientPortname>
<value>2181value>
property>
<property>
<name>hbase.master.info.portname>
<value>60010value>
property>
<property>
<name>hbase.cluster.distributedname>
<value>truevalue>
<description>多台hbase开启此参数description>
property>
configuration>
5、分发
[root@node1 conf]# scp -rp /data/bigdata/src/hbase-1.2.6 node2:/data/bigdata/src/
[root@node1 conf]# scp -rp /data/bigdata/src/hbase-1.2.6 node3:/data/bigdata/src/
# 创建软连接
[root@node2 ~]# ln -s /data/bigdata/src/hbase-1.2.6 /data/bigdata/hbase
[root@node3 ~]# ln -s /data/bigdata/src/hbase-1.2.6 /data/bigdata/hbase
6、启动hbase
[root@node1 hadoop]# cd /data/bigdata/hbase/bin
[root@node1 bin]# ./start-hbase.sh
[root@node1 bin]# jps
5443 DFSZKFailoverController
1092 HRegionServer # hbase进程
904 HMaster # hbase主节点
4664 JournalNode
23993 QuorumPeerMain
14730 Master
7227 NodeManager
4988 NameNode
14877 Worker
1917 Jps
6495 DataNode
[root@node1 bin]#
到目前为止所启动的进程：
| \ | node1 | node2 | node3 | node4 | node5 |
|---|---|---|---|---|---|
| JDK | ✔ | ✔ | ✔ | ✔ | ✔ |
| QuorumPeerMain | ✔ | ✔ | ✔ | ||
| JournalNode | ✔ | ✔ | ✔ | ||
| NameNode | ✔ | ✔ | |||
| DFSZKFailoverController | ✔ | ✔ | |||
| DataNode | ✔ | ✔ | ✔ | ✔ | ✔ |
| NodeManager | ✔ | ✔ | ✔ | ✔ | ✔ |
| ResourceManager | ✔ | ✔ | |||
| Master | ✔ | ||||
| Worker | ✔ | ✔ | ✔ | ✔ | ✔ |
| HistoryServer | ✔ | ||||
| HMaster | ✔ | ||||
| HRegionServer | ✔ | ✔ | ✔ |
Hbase web页面http://192.168.1.101:16030
Hbase Master URL:http://192.168.1.101:60010
# 测试
[root@node1 bin]# ./hbase shell
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/data/bigdata/src/hbase-1.2.6/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/data/bigdata/src/hadoop-2.7.6/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
HBase Shell; enter 'help' for list of supported commands.
Type "exit" to leave the HBase Shell
Version 1.2.6, rUnknown, Mon May 29 02:25:32 CDT 2017
hbase(main):001:0> list # 输入命令list
TABLE
0 row(s) in 0.2670 seconds
=> []
hbase(main):002:0> quit
[root@node1 bin]#
十、kafka
官方文档
kafka实战最佳经验
1、解压创建环境变量
[root@node4 conf]# tar -zxvf /data/tools/kafka_2.11-1.1.0.tgz -C /data/bigdata/src/
[root@node4 conf]# ln -s /data/bigdata/src/kafka_2.11-1.1.0 /data/bigdata/kafka
# 添加环境变量
[root@node4 ~]# echo -e "\n# kafka\nexport KAFKA_HOME=/data/bigdata/kafka\nexport PATH=\$KAFKA_HOME/bin:\$PATH" >> /etc/profile.d/bigdata_path.sh
[root@node4 ~]# cat /etc/profile.d/bigdata_path.sh
# zookeeper
export ZOOKEEPER_HOME=/data/bigdata/zookeeper
export PATH=$ZOOKEEPER_HOME/bin:$PATH
# hadoop
export HADOOP_HOME=/data/bigdata/hadoop
export PATH=$HADOOP_HOME/bin:$HADOOP_HOME/sbin:$PATH
# hbase
export HBASE_HOME=/data/bigdata/hbase
export PATH=$HBASE_HOME/bin:$PATH
# scala
export scala_HOME=/data/bigdata/scala
export PATH=$scala_HOME/bin:$PATH
# spark
export SPARK_HOME=/data/bigdata/spark
export PATH=$SPARK_HOME/bin:$PATH
# kafka
export KAFKA_HOME=/data/bigdata/kafka
export PATH=$KAFKA_HOME/bin:$PATH
# 生效
[root@node4 conf]# source /etc/profile
2、修改server.properties配置文件：
[root@node4 ~]# cd /data/bigdata/kafka/config/ # 进入conf目录
[root@node4 conf]# cp server.properties{,.bak} # 备份配置文件
[root@node4 conf]# vim server.properties
broker.id=1
listeners=PLAINTEXT://node4:9092
advertised.listeners=PLAINTEXT://node4:9092
log.dirs=/data/bigdata/kafka/logs
zookeeper.connect=node1:2181,node2:2181,node3:2181
[root@node4 conf]# mkdir -p /data/bigdata/kafka/logs
3、分发
[root@node4 conf]# scp -rp /data/bigdata/src/kafka_2.11-1.1.0 node5: /data/bigdata/src/
# 子节点
[root@node5 ~]# ln -s /data/bigdata/src/kafka_2.11-1.1.0 /data/bigdata/kafka
[root@node5 ~]# mkdir -p /data/bigdata/kafka/logs
# 修改每个server.properties文件中的broker.id
[root@node5 ~]# cd /data/bigdata/kafka/
[root@node5 kafka]# vim ./config/server.properties
broker.id=2
listeners=PLAINTEXT://node5:9092
advertised.listeners=PLAINTEXT://node5:9092
# 查看
[root@node1 conf]# ansible kafka -m shell -a '$(which egrep) --color=auto "^broker.id|^listeners|^advertised.listeners" ${KAFKA_HOME}/config/server.properties'
4、启动
[root@node4 kafka]# ./bin/kafka-server-start.sh config/server.properties # 单个节点前台运行
[2018-06-05 13:32:35,323] INFO Registered kafka:type=kafka.Log4jController MBean (kafka.utils.Log4jControllerRegistration$)
[2018-06-05 13:32:35,672] INFO starting (kafka.server.KafkaServer)
[2018-06-05 13:32:35,673] INFO Connecting to zookeeper on node1:2181,node2:2181,node3:2181 (kafka.server.KafkaServer)
[2018-06-05 13:32:35,692] INFO [ZooKeeperClient] Initializing a new session to node1:2181,node2:2181,node3:2181. (kafka.zookeeper.ZooKeeperClient)
[2018-06-05 13:32:35,698] INFO Client environment:zookeeper.version=3.4.10-39d3a4f269333c922ed3db283be479f9deacaa0f, built on 03/23/2017 10:13 GMT
..........................................
省略若干
...........................................
[2018-06-05 13:33:38,920] INFO Terminating process due to signal SIGINT (kafka.Kafka$)
[2018-06-05 13:33:39,168] INFO [ThrottledRequestReaper-Produce]: Stopped (kafka.server.ClientQuotaManager$ThrottledRequestReaper)
[2018-06-05 13:33:39,168] INFO [ThrottledRequestReaper-Produce]: Shutdown completed (kafka.server.ClientQuotaManager$ThrottledRequestReaper)
[2018-06-05 13:33:39,168] INFO [ThrottledRequestReaper-Request]: Shutting down (kafka.server.ClientQuotaManager$ThrottledRequestReaper)
[2018-06-05 13:33:39,168] INFO [ThrottledRequestReaper-Request]: Stopped (kafka.server.ClientQuotaManager$ThrottledRequestReaper)
[2018-06-05 13:33:39,168] INFO [ThrottledRequestReaper-Request]: Shutdown completed (kafka.server.ClientQuotaManager$ThrottledRequestReaper)
[2018-06-05 13:33:39,169] INFO [SocketServer brokerId=1] Shutting down socket server (kafka.network.SocketServer)
[2018-06-05 13:33:39,193] INFO [SocketServer brokerId=1] Shutdown completed (kafka.network.SocketServer)
[2018-06-05 13:33:39,199] INFO [KafkaServer id=1] shut down completed (kafka.server.KafkaServer)
[root@node4 kafka]# ./bin/kafka-server-start.sh -daemon config/server.properties # 后台启动单个节点，其它kafka也要启动，进程名为：Kafka
到目前为止所启动的进程：
| \ | node1 | node2 | node3 | node4 | node5 |
|---|---|---|---|---|---|
| JDK | ✔ | ✔ | ✔ | ✔ | ✔ |
| QuorumPeerMain | ✔ | ✔ | ✔ | ||
| JournalNode | ✔ | ✔ | ✔ | ||
| NameNode | ✔ | ✔ | |||
| DFSZKFailoverController | ✔ | ✔ | |||
| DataNode | ✔ | ✔ | ✔ | ✔ | ✔ |
| NodeManager | ✔ | ✔ | ✔ | ✔ | ✔ |
| ResourceManager | ✔ | ✔ | |||
| HMaster | ✔ | ||||
| HRegionServer | ✔ | ✔ | ✔ | ||
| HistoryServer | ✔ | ||||
| Master | ✔ | ||||
| Worker | ✔ | ✔ | ✔ | ✔ | ✔ |
| Kafka | ✔ | ✔ |
Kafka并没有提供同时启动集群中所有节点的执行脚本，在生产中一个Kafka集群往往会有多个节点，若逐个节点启动稍微有些麻烦，自定义一个脚本用来启动集群中所有节点，如下：
[root@node1 bigdata]# cat kafka_cluster_start.sh
#!/bin/bash
brokers="node4 node5"
KAFKA_HOME="/data/bigdata/kafka"
for broker in $brokers
do
ssh $broker -C "source /etc/profile; cd ${KAFKA_HOME}/bin && ./kafka-server-start.sh -daemon ../config/server.properties"
if [ $? -eq 0 ]; then
echo "INFO:[${broker}] Start successfully "
fi
done
[root@node1 bigdata]#
5、测试
创建主题：（指明要连接的zookeeper）例如主题名称为：TestTopic
[root@node4 kafka]# ./bin/kafka-topics.sh --create --zookeeper node1:2181,node2:2181,node3:2181 --replication-factor 1 --partitions 1 --topic TestTopic
Created topic "TestTopic". # 表示创建成功
查看主题：
[root@node4 kafka]# ./bin/kafka-topics.sh --list --zookeeper node1:2181,node2:2181,node3:2181
TestTopic # 可以看到所有已创建的主题
任选一台，创建生产者：（kafka集群用户）
[root@node4 kafka]# ./bin/kafka-console-producer.sh --broker-list node4:9092,node5:9092 --topic TestTopic
>hi
>hello 1
>hello 2
>
另一台，创建消费者
[root@node5 kafka]# ./bin/kafka-console-consumer.sh --bootstrap-server node4:9092,node5:9092 --from-beginning --topic TestTopic
hi
hello 1
hello 2
生产者输入一些数据，看消费者是否显示生产者所输入的数据。
6、关闭
[root@node4 kafka]# ./bin/kafka-server-stop.sh # 关闭，其它kafka也要关闭，
有时候不管用，显示“No kafka server to stop”，
失败的原因是kafka-server-stop.sh脚本里的ps ax | grep -i 'kafka.Kafka' | grep Java | grep -v grep | awk '{print $1}'命令在我所使用的操作系统中并不能得到Kafka进程的PID：
因此这里将kafka-server-stop.sh脚本查找PID的命令修改如下：
#PIDS=$(ps ax | grep -i 'kafka\.Kafka' | grep java | grep -v grep | awk '{print $1}') # 注掉，改为下面命令
PIDS=$(jps | grep -i 'Kafka' |awk '{print $1}')
Kafka也同样没有提供关闭集群操作的脚本。这里我提供一个用来关闭Kafka集群的脚本（可以放在任意一条节点上）：
[root@node1 bigdata]# cat kafka_cluster_stop.sh
#!/bin/bash
brokers="node4 node5"
KAFKA_HOME="/data/bigdata/kafka"
for broker in $brokers
do
ssh $broker -C "cd ${KAFKA_HOME}/bin && ./kafka-server-stop.sh"
if [ $? -eq 0 ]; then
echo "INFO:[${broker}] shut down completed "
fi
done
[root@node1 bigdata]# chmod +x kafka-cluster-stop.sh
十一、hive
官方文档
1、安装mysql数据库
参考：https://blog.51cto.com/moerjinrong/2092614
# 新建hive用户及metastore库
root@node2 14:37: [(none)]> grant all privileges on *.* to 'hive'@'192.168.1.%' identified by '123456';
Query OK, 0 rows affected, 1 warning (0.00 sec)
root@node2 15:14: [(none)]> create database metastore; # 待定
Query OK, 1 row affected (0.01 sec)
2、解压添加环境变量
[root@node2 ~]# tar -zxvf /data/tools/apache-hive-2.3.3-bin.tar.gz -C /data/bigdata/src/
[root@node2 ~]# ln -s /data/bigdata/src/apache-hive-2.3.3-bin /data/bigdata/hive
# 添加环境变量
[root@node2 ~]# echo -e "\n# hive\nexport HIVE_HOME=/data/bigdata/hive\nexport PATH=\$HIVE_HOME/bin:\$PATH" >> /etc/profile.d/bigdata_path.sh
[root@node2 ~]# cat /etc/profile.d/bigdata_path.sh
# zookeeper
export ZOOKEEPER_HOME=/data/bigdata/zookeeper
export PATH=$ZOOKEEPER_HOME/bin:$PATH
# hadoop
export HADOOP_HOME=/data/bigdata/hadoop
export PATH=$HADOOP_HOME/bin:$HADOOP_HOME/sbin:$PATH
# hbase
export HBASE_HOME=/data/bigdata/hbase
export PATH=$HBASE_HOME/bin:$PATH
# scala
export scala_HOME=/data/bigdata/scala
export PATH=$scala_HOME/bin:$PATH
# spark
export SPARK_HOME=/data/bigdata/spark
export PATH=$SPARK_HOME/bin:$PATH
# kafka
export KAFKA_HOME=/data/bigdata/kafka
export PATH=$KAFKA_HOME/bin:$PATH
# hive
export HIVE_HOME=/data/bigdata/hive
export PATH=$HIVE_HOME/bin:$PATH"
# 生效
[root@node2 ~]# source /etc/profile
3、hdfs上新建目录
在hdfs中新建目录/user/hive/warehouse
首先启动hadoop任务
hdfs dfs -mkdir /tmp
hdfs dfs -mkdir /user
hdfs dfs -mkdir /user/hive
hdfs dfs -mkdir /user/hive/warehouse
hadoop fs -chmod g+w /tmp
hadoop fs -chmod g+w /user/hive/warehouse
# 将mysql的驱动jar包mysql-connector-java-5.1.46.jar拷入hive的lib目录下面，没有就下载：
wget -P $HIVE_HOME/lib http://central.maven.org/maven2/mysql/mysql-connector-java/5.1.46/mysql-connector-java-5.1.46.jar
4、修改server.properties配置文件：
[root@node2 ~]# cd /data/bigdata/hive/conf/
[root@node2 conf]# cp hive-default.xml.template hive-site.xml
[root@node2 conf]# vim hive-site.xml
# 修改下列属性值（通过/指令寻找，如果第一个定位不正确，n寻找下一个）
<property>
<name>javax.jdo.option.ConnectionURLname>
<value>jdbc:mysql://192.168.1.102:3306/hive?createDatabaseIfNotExist=true&useSSL=falsevalue> # mysql没有开启ssl
<description>
JDBC connect string for a JDBC metastore;
'?'符号是在URL后通过get方法传递参数的起始标志，
多个参数之间可用'&'符号连接，因为这些字符对于HTML有特殊意义，
所以在Java中要用到转义字符使用它，而&在HTML中就会被转义为'&'符号，用于参数连接。
description>
property>
<property>
<name>javax.jdo.option.ConnectionDriverNamename>
<value>com.mysql.jdbc.Drivervalue>
<description>Driver class name for a JDBC metastoredescription>
property>
<property>
<name>javax.jdo.option.ConnectionUserNamename>
<value>hivevalue>
<description>Username to use against metastore databasedescription>
property>
<property>
<name>javax.jdo.option.ConnectionPasswordname>
<value>123456value>
<description>password to use against metastore databasedescription>
property>
<property>
<name>hive.metastore.warehouse.dirname>
<value>/data/bigdata/hive/warehousevalue>
property>
<property>
<name>hive.metastore.localname>
<value>truevalue>
property>
<property>
<name>hive.exec.local.scratchdirname>
<value>/data/bigdata/hive/tmpvalue>
<description>Local scratch space for Hive jobsdescription>
property>
<property>
<name>hive.downloaded.resources.dirname>
<value>/data/bigdata/hive/tmp/resourcesvalue>
<description>Temporary local directory for added resources in the remote file system.description>
property>
<property>
<name>hive.querylog.locationname>
<value>/data/bigdata/hive/tmpvalue>
<description>Location of Hive run time structured log filedescription>
property>
<property>
<name>hive.server2.logging.operation.log.locationname>
<value>/data/bigdata/hive/tmp/operation_logsvalue>
<description>Top level directory where operation logs are stored if logging functionality is enableddescription>
property>
注意：由于HTML格式问题，上面jdbc的URL中的&改为照片中红色下划线的符号
# 创建指定目录
[root@node2 conf]# mkdir -pv /data/bigdata/hive/{tmp/{operation_logs,resources},warehouse}
5、初始化并运行
# 使用schematool 初始化metastore的schema：
[root@node2 conf]# schematool -initSchema -dbType mysql
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/data/bigdata/src/apache-hive-2.3.3-bin/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/data/bigdata/src/hadoop-2.7.6/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
Metastore connection URL: jdbc:mysql://127.0.0.1:3306/metastore?useSSL=false
Metastore Connection Driver : com.mysql.jdbc.Driver
Metastore connection User: hive
Starting metastore schema initialization to 2.3.0
Initialization script hive-schema-2.3.0.mysql.sql
Initialization script completed
schemaTool completed
[root@node2 conf]#
# 运行hive
[root@node2 conf]# hive # 对应RunJar进程
hive> show databases;
OK
default
Time taken: 1.881 seconds, Fetched: 1 row(s)
hive> use default;
OK
Time taken: 0.081 seconds
hive> create table kylin_test(test_count int);
OK
Time taken: 2.9 seconds
hive> show tables;
OK
Time taken: 0.151 seconds, Fetched: 1 row(s)
hive> quit;
到目前为止所启动的进程：
| \ | node1 | node2 | node3 | node4 | node5 |
|---|---|---|---|---|---|
| JDK | ✔ | ✔ | ✔ | ✔ | ✔ |
| QuorumPeerMain | ✔ | ✔ | ✔ | ||
| JournalNode | ✔ | ✔ | ✔ | ||
| NameNode | ✔ | ✔ | |||
| DFSZKFailoverController | ✔ | ✔ | |||
| DataNode | ✔ | ✔ | ✔ | ✔ | ✔ |
| NodeManager | ✔ | ✔ | ✔ | ✔ | ✔ |
| ResourceManager | ✔ | ✔ | |||
| HMaster | ✔ | ||||
| HRegionServer | ✔ | ✔ | ✔ | ||
| HistoryServer | ✔ | ||||
| Master | ✔ | ||||
| Worker | ✔ | ✔ | ✔ | ✔ | ✔ |
| Kafka | ✔ | ✔ | |||
| RunJar(# 启动hive时才有) | ✔ |
十二、kylin
官方文档
1、安装前准备
安装kylin前确保：hadoop 2.4+、hbase 0.13+、hive 0.98+，1.*已经安装并启动。
Hive需要启动metastore和hiveserver2。
Apache Kylin同样可以使用集群部署，但使用集群部署并不能增加计算速度
因为计算过程使用MapReduce引擎，与Kylin自身无关，而是主要为查询提供负载均衡。本次采用单节点。
2、解压并创建环境变量
[root@node2 ~]# tar zxvf /data/tools/apache-kylin-2.3.1-hbase1x-bin.tar.gz -C /data/bigdata/src/
[root@node2 ~]# ln -s /data/bigdata/src/apache-kylin-2.3.1-bin/ /data/bigdata/kylin
# 添加环境变量
[root@node2 ~]# echo -e "\n# kylin\nexport KYLIN_HOME=/data/bigdata/kylin\nexport PATH=\$KYLIN_HOME/bin:\$PATH" >> /etc/profile.d/bigdata_path.sh
[root@node2 ~]# cat /etc/profile.d/bigdata_path.sh
# zookeeper
export ZOOKEEPER_HOME=/data/bigdata/zookeeper
export PATH=$ZOOKEEPER_HOME/bin:$PATH
# hadoop
export HADOOP_HOME=/data/bigdata/hadoop
export PATH=$HADOOP_HOME/bin:$HADOOP_HOME/sbin:$PATH
# hbase
export HBASE_HOME=/data/bigdata/hbase
export PATH=$HBASE_HOME/bin:$PATH
# scala
export scala_HOME=/data/bigdata/scala
export PATH=$scala_HOME/bin:$PATH
# spark
export SPARK_HOME=/data/bigdata/spark
export PATH=$SPARK_HOME/bin:$PATH
# kafka
export KAFKA_HOME=/data/bigdata/kafka
export PATH=$KAFKA_HOME/bin:$PATH
# kylin
export KYLIN_HOME=/data/bigdata/kylin
export PATH=$KYLIN_HOME/bin:$PATH"
# 生效
[root@node2 ~]# source /etc/profile
3、复制hive的相关jar到kylin
将hive安装目录lib目录中的所有jar包复制到kylin安装目录下的lib目录中。
[root@node2 ~]# cp -a /data/bigdata/hive/lib/* /data/bigdata/kylin/lib/
4、配置Kylin使用的Hive数据库：
[root@node2 ~]# cd /data/bigdata/kylin/conf
[root@node2 conf]# vim kylin.properties
kylin.server.cluster-servers=node2:7070 # kylin集群设置，修改主机名或ip，端口
kylin.job.jar=$KYLIN_HOME/lib/kylin-job-2.3.1.jar # 修改jar包版本及路径
kylin.coprocessor.local.jar=$KYLIN_HOME/lib/kylin-coprocessor-2.3.1.jar # 修改jar包版本及路径
# List of web servers in use, this enables one web server instance to sync up with other servers
kylin.rest.servers=node2:7070
## 配置Kylin使用的Hive数据库，这里配置在Hive中使用的schema，改为当前用户
kylin.job.hive.database.for.intermediatetable=root
5、如果没有启动https，请关闭
[root@node2 ~]# cd /data/bigdata/kylin/tomcat/conf
[root@node2 conf]# cp -a server.xml{,_$(date +%F)}
[root@node2 conf]# vim server.xml
85 maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
改为：
85 maxThreads="150" SSLEnabled="false" scheme="https" secure="false"
如果不关闭，会报如下错误
SEVERE: Failed to load keystore type JKS with path conf/.keystore due to /data/bigdata/kylin/tomcat/conf/.keystore (No such file or directory)
java.io.FileNotFoundException: /data/bigdata/kylin/tomcat/conf/.keystore (No such file or directory)
6、修改$KYLIN_HOME/bin/kylin.sh
[root@node2 conf]# vim ../bin/kylin.sh
export KYLIN_HOME=/data/bigdata/kylin
export CATALINA_HOME=/data/bigdata/kylin/tomcat
export PATH=$CATALINA_HOME/bin:$PATH
export HCAT_HOME=$HIVE_HOME/hcatalog
export hive_dependency=$HIVE_HOME/conf:$HIVE_HOME/lib/*:$HCAT_HOME/share/hcatalog/hive-hcatalog-core-2.3.3.jar
export HBASE_CLASSPATH_PREFIX=$CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/tomcatjuli.jar:$CATALINA_HOME/lib/*:$hive_dependency:$HBASE_CLASSPATH_PREFIX
#使用HDFS超级用户在HDFS上为Kylin创建工作目录，并赋权给服务器登录名
#[root@node2 conf]# hdfs dfs -mkdir /kylin
#[root@node2 conf]# hdfs dfs -chown -R root:root /kylin
7、检查kylin依赖
进入bin目录下分别执行
[root@node2 bin]# cd $KYLIN_HOME/bin
[root@node2 bin]# ./check-env.sh
Retrieving hadoop conf dir...
KYLIN_HOME is set to /data/bigdata/kylin
[root@node2 bin]# ./find-hive-dependency.sh
Retrieving hive dependency...
[root@node2 bin]# ./find-hbase-dependency.sh
Retrieving hbase dependency...
8、启动kylin服务
在kylin安装根目录下执行
[root@node2 bin]# ./kylin.sh start
Retrieving hadoop conf dir...
KYLIN_HOME is set to /data/bigdata/kylin
Retrieving hive dependency...
Retrieving hbase dependency...
Retrieving hadoop conf dir...
Retrieving kafka dependency...
Retrieving Spark dependency...
Start to check whether we need to migrate acl tables
..........................................
省略若干
...........................................
2018-06-05 17:12:10,111 INFO [Thread-6] zookeeper.ZooKeeper:684 : Session: 0x300346e6b9e000d closed
2018-06-05 17:12:10,111 INFO [main-EventThread] zookeeper.ClientCnxn:512 : EventThread shut down
2018-06-05 17:12:10,210 INFO [close-hbase-conn] client.ConnectionManager$HConnectionImplementation:2068 : Closing master protocol: MasterService
2018-06-05 17:12:10,211 INFO [close-hbase-conn] client.ConnectionManager$HConnectionImplementation:1676 : Closing zookeeper sessionid=0x20034776a7c0004
2018-06-05 17:12:10,214 INFO [close-hbase-conn] zookeeper.ZooKeeper:684 : Session: 0x20034776a7c0004 closed
2018-06-05 17:12:10,214 INFO [main-EventThread] zookeeper.ClientCnxn:512 : EventThread shut down
A new Kylin instance is started by root. To stop it, run 'kylin.sh stop'
Check the log at /data/bigdata/kylin/logs/kylin.log
Web UI is at http://<hostname>:7070/kylin
[root@node2 bin]#
到目前为止所启动的进程：
| \ | node1 | node2 | node3 | node4 | node5 |
|---|---|---|---|---|---|
| JDK | ✔ | ✔ | ✔ | ✔ | ✔ |
| QuorumPeerMain | ✔ | ✔ | ✔ | ||
| JournalNode | ✔ | ✔ | ✔ | ||
| NameNode | ✔ | ✔ | |||
| DFSZKFailoverController | ✔ | ✔ | |||
| DataNode | ✔ | ✔ | ✔ | ✔ | ✔ |
| NodeManager | ✔ | ✔ | ✔ | ✔ | ✔ |
| ResourceManager | ✔ | ✔ | |||
| HMaster | ✔ | ||||
| HRegionServer | ✔ | ✔ | ✔ | ||
| HistoryServer | ✔ | ||||
| Master | ✔ | ||||
| Worker | ✔ | ✔ | ✔ | ✔ | ✔ |
| Kafka | ✔ | ✔ | |||
| RunJar(# 启动hive时才有) | ✔ | ||||
| RunJar(# kylin进程) | ✔ | ✔ |
服务启动后，浏览器访问地址：http://IP:7070/kylin/
用户名：ADMIN
密码：KYLIN
9、配置hive数据源
1.配置数据源
（1）依次选择 Model -> Data Source -> Load Hive Table
（2）输入 hive 中数据库的表名格式为： 数据库名.数据表名
如：db_hiveTest.student ，然后点击Sync即可。
添加成功后，效果如下图：
10、常见错误
1、界面无法同步hive表元数据
解决方法，在kylin安装目录下：
执行命令：vim ./bin/kylin.sh 需要对此脚本做以下修改：
export HBASE_CLASSPATH_PREFIX=${tomcat_root}/bin/bootstrap.jar:${tomcat_root}/bin/tomcat-juli.jar:${tomcat_root}/lib/*:$hive_dependency:$HBASE_CLASSPATH_PREFIX# 在路径中添加$hive_dependency。
十三、记一次日常启动
1、zookeeper:
[root@node1 ~]# cd /data/bigdata/
[root@node1 bigdata]# ./zookeeper_all_op.sh start
ZooKeeper JMX enabled by default
Using config: /data/bigdata/src/zookeeper-3.4.12/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
node1 zookeeper start done
ZooKeeper JMX enabled by default
Using config: /data/bigdata/src/zookeeper-3.4.12/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
node2 zookeeper start done
ZooKeeper JMX enabled by default
Using config: /data/bigdata/src/zookeeper-3.4.12/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
node3 zookeeper start done
[root@node1 bigdata]# ./zookeeper_all_op.sh status
ZooKeeper JMX enabled by default
Using config: /data/bigdata/src/zookeeper-3.4.12/bin/../conf/zoo.cfg
Mode: follower
node1 zookeeper status done
ZooKeeper JMX enabled by default
Using config: /data/bigdata/src/zookeeper-3.4.12/bin/../conf/zoo.cfg
Mode: leader
node2 zookeeper status done
ZooKeeper JMX enabled by default
Using config: /data/bigdata/src/zookeeper-3.4.12/bin/../conf/zoo.cfg
Mode: follower
node3 zookeeper status done
可以看到一个leader，其它为follower就可以*
2、hadoop:
[root@node1 bigdata]# cd /data/bigdata/src/hadoop-2.7.6/sbin/
[root@node1 sbin]# ./start-all.sh
This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh
Starting namenodes on [node1 node2]
node1: starting namenode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-namenode-node1.out
node2: starting namenode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-namenode-node2.out
node1: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node1.out
node2: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node2.out
node5: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node5.out
node3: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node3.out
node4: starting datanode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-datanode-node4.out
Starting journal nodes [node1 node2 node3]
node1: starting journalnode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-journalnode-node1.out
node2: starting journalnode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-journalnode-node2.out
node3: starting journalnode, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-journalnode-node3.out
Starting ZK Failover Controllers on NN hosts [node1 node2]
node2: starting zkfc, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-zkfc-node2.out
node1: starting zkfc, logging to /data/bigdata/src/hadoop-2.7.6/logs/hadoop-root-zkfc-node1.out
starting yarn daemons
starting resourcemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-resourcemanager-node1.out
node1: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node1.out
node3: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node3.out
node5: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node5.out
node2: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node2.out
node4: starting nodemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-nodemanager-node4.out
[root@node1 sbin]# jps
16418 QuorumPeerMain
18196 Jps
17047 NameNode
17194 DataNode
17709 DFSZKFailoverController
17469 JournalNode
17999 NodeManager
[root@node1 sbin]#
没有启动的去相应服务器下单独启动
resourcemanager:需单独启动
[root@node3 sbin]# ./yarn-daemon.sh start resourcemanager
starting resourcemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-resourcemanager-node3.out
[root@node3 sbin]# jps
15968 Jps
14264 QuorumPeerMain
14872 NodeManager
14634 DataNode
15723 ResourceManager
14749 JournalNode
[root@node3 sbin]#
[root@node4 sbin]# ./yarn-daemon.sh start resourcemanager
starting resourcemanager, logging to /data/bigdata/src/hadoop-2.7.6/logs/yarn-root-resourcemanager-node4.out
[root@node4 sbin]# jps
2995 NodeManager
4004 ResourceManager
4091 Jps
2813 DataNode
[root@node4 sbin]#
3、spark
[root@node1 sbin]# cd /data/bigdata/src/spark-2.1.2-bin-hadoop2.7/sbin/
[root@node1 sbin]# ./start-all.sh
starting org.apache.spark.deploy.master.Master, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.master.Master-1-node1.out
node5: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node5.out
node1: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node1.out
node4: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node4.out
node2: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node2.out
node3: starting org.apache.spark.deploy.worker.Worker, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.worker.Worker-1-node3.out
[root@node1 sbin]# ./start-history-server.sh
starting org.apache.spark.deploy.history.HistoryServer, logging to /data/bigdata/spark/logs/spark-root-org.apache.spark.deploy.history.HistoryServer-1-node1.out
[root@node1 sbin]#
4、hbase
[root@node1 ~]# cd /data/bigdata/src/hbase-1.2.6/bin/
[root@node1 bin]# ./start-hbase.sh
starting master, logging to /data/bigdata/hbase/logs/hbase-root-master-node1.out
node3: starting regionserver, logging to /data/bigdata/hbase/logs/hbase-root-regionserver-node3.out
node2: starting regionserver, logging to /data/bigdata/hbase/logs/hbase-root-regionserver-node2.out
node1: starting regionserver, logging to /data/bigdata/hbase/logs/hbase-root-regionserver-node1.out
[root@node1 bin]#