安装cloudera hadoop

本文档详细介绍了在CentOS 7.2环境下安装Cloudera Hadoop集群的步骤,包括配置节点间的免密SSH登录,关闭SELinux和防火墙,设置NTP服务,安装必要软件,配置Cloudera Manager YUM源,以及使用内置Postgres数据库的安装流程。最后提供了相关参考资料和故障处理链接。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

环境:centos 7.2 node136-node140 主节点:node136 从节点: node137-node140
软件获取 https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.14.2/RPMS/x86_64/
配置所有节点间免密码ssh登录
所有节点关闭selinux与防火墙
[root@node136 ~]# sed -i -e ‘s/SELINUX=enforcing/SELINUX=disabled/g’ /etc/sysconfig/selinux
[root@node136 ~]# sed -i -e ‘s/SELINUX=enforcing/SELINUX=disabled/g’ /etc/selinux/config
[root@node136 ~]# systemctl disable firewalld

在所有节点上开启ntpd服务,同步同一个时间服务器的时间
[root@node136 ~]# vim /etc/ntp.conf 配置为内网中ntp服务器的地址
[root@node136 ~]# systemctl start ntpd
[root@node136 ~]# systemctl enable ntpd
如果ntp服务器有问题,解决后需要重启cloudera-scm-server与cloudera-scm-agent
在所有节点上进行安装
[root@node136 ~]# yum -y install sysstat vim tree wget lrzsz screen gcc python-devel gcc-c++ vim ntpdate libyaml
libyaml-devel python-setuptools ntp fuse httpd mod_ssl openssl-devel python-psycopg2 MySQL-python redhat-lsb postgresql-server
[root@node136 ~]# cat setup_cloudera_env.sh

#!/bin/bash
echo never > /sys/kernel/mm/transparent_hugepage/defrag
echo never > /sys/kernel/mm/transparent_hugepage/enabled
echo    "* soft nofile 65536         " >>  /etc/security/limits.conf
echo    "* hard nofile 65536         " >>  /etc/security/limits.conf
echo    "root soft nofile 65536      " >>  /etc/security/limits.conf
echo    "root hard nofile 65536      " >>  /etc/security/limits.conf
echo    "* soft memlock unlimited    " >>  /etc/security/limits.conf
echo    "* hard memlock unlimited    " >>  /etc/security/limits.conf
echo    "root soft memlock unlimited " >>  /etc/security/limits.conf
echo    "root hard memlock unlimited " >>  /etc/security/limits.conf
echo    "* soft as unlimited         " >>  /etc/security/limits.conf
echo    "* hard as unlimited         " >>  /etc/security/limits.conf
echo    "root soft as unlimited      " >>  /etc/security/limits.conf
echo    "root hard as unlimited      " >>  /etc/security/limits.conf
echo "vm.max_map_count = 131072" >> /etc/sysctl.conf
echo "vm.swappiness=1" >> /etc/sysctl.conf
sysctl -p
rpm -ivh  /root/Hadoop/cloudera-manager-daemons-5.14.2-1.cm5142.p0.8.el7.x86_64.rpm
rpm -ivh  /root/Hadoop/cloudera-manager-server-5.14.2-1.cm5142.p0.8.el7.x86_64.rpm
rpm -ivh  /root/Hadoop/cloudera-manager-server-db-2-5.14.2-1.cm5142.p0.8.el7.x86_64.rpm
rpm -ivh  /root/Hadoop/enterprise-debuginfo-5.14.2-1.cm5142.p0.8.el7.x86_64.rpm
rpm -ivh  /root/Hadoop/cloudera-manager-agent-5.14.2-1.cm5142.p0.8.el7.x86_64.rpm

[root@node136 ~]# sh -x setup_cloudera_env.sh
可以只在agent节点安装cloudera-manager-agent与cloudera-manager-daemons的rpm,但这里对所有节点安装所有rpm包。
[root@node136 ~]# mkdir -p /opt/cloudera/parcel-repo

[root@node136 ~]# cp -rpv Hadoop/CDH-5.14.2-1.cdh5.14.2.p0.3-el7.parcel /opt/cloudera/parcel-repo/
“Hadoop/CDH-5.14.2-1.cdh5.14.2.p0.3-el7.parcel” -> “/opt/cloudera/parcel-repo/CDH-5.14.2-1.cdh5.14.2.p0.3-el7.parcel”
[root@node136 ~]# cp -rpv Hadoop/manifest.json /opt/cloudera/parcel-repo/
“Hadoop/manifest.json” -> "/opt/cloudera/parcel-repo/manifest.json
[root@node136 ~]# cp -rpv Hadoop/CDH-5.14.2-1.cdh5.14.2.p0.3-el7.parcel.sha1 /opt/cloudera/parcel-repo/CDH-5.14.2-1.cdh5.14.2.p0.3-el7.parcel.sha
“Hadoop/CDH-5.14.2-1.cdh5.14.2.p0.3-el7.parcel.sha1” -> “/opt/cloudera/parcel-repo/CDH-5.14.2-1.cdh5.14.2.p0.3-el7.parcel.sha”

[root@node136 ~]# yum -y erase java
[root@node136 ~]# rpm -ivh Hadoop/jdk-8u172-linux-x64.rpm
准备中… ################################# [100%]
正在升级/安装…
1:jdk1.8-2000:1.8.0_172-fcs ################################# [100%]
Unpacking JAR files…
tools.jar…
plugin.jar…
javaws.jar…
deploy.jar…
rt.jar…
jsse.jar…
charsets.jar…
localedata.jar…
[root@node137 ~]# echo “export JAVA_HOME=/usr/java/jdk1.8.0_172-amd64/” >> /etc/profile
[root@node137 ~]# source /etc/profile
[root@node136 ~]# ls /etc/init.d/|grep clouder
cloudera-scm-agent
cloudera-scm-server
cloudera-scm-server-db

配置好内网的yum源
[root@node136 ~]# cp Hadoop/cloudera-manager.repo /etc/yum.repos.d/cloudera-manager.repo
[root@node136 ~]# cat /etc/yum.repos.d/cloudera-manager.repo
[cloudera-manager]
name=Cloudera Manager
baseurl=http://10.98.131.70/cm5/redhat/7/x86_64/cm/5/
gpgkey =http://10.98.131.70/cm5/redhat/7/x86_64/cm/RPM-GPG-KEY-cloudera
gpgcheck = 1
[root@node136 ~]# chmod +x ./Hadoop/cloudera-manager-installer.bin
[root@node136 ~]# ./Hadoop/cloudera-manager-installer.bin
在web页面上一步步安装就可以了。
在这里没有手动启动cloudera-scm-server与cloudera-scm-agent服务,有些文章说需要手动启动。
使用了内嵌postgres数据库,在登陆首页时会提示不是生产环境安装。

完成后查看状态如下:
主节点:

[root@node136 ~]# ps -ef|grep postgres
clouder+  4213  4714  0 4月27 ?       00:01:23 postgres: hive1 hive1 10.98.131.137(52180) idle
clouder+  4214  4714  0 4月27 ?       00:01:23 postgres: hive1 hive1 10.98.131.137(52181) idle
clouder+  4215  4714  0 4月27 ?       00:01:22 postgres: hive1 hive1 10.98.131.138(58389) idle
clouder+  4216  4714  0 4月27 ?       00:01:21 postgres: hive1 hive1 10.98.131.138(58390) idle
clouder+  4230  4714  0 4月27 ?       00:01:29 postgres: hive1 hive1 10.98.131.136(58431) idle
clouder+  4231  4714  0 4月27 ?       00:01:29 postgres: hive1 hive1 10.98.131.136(58432) idle
clouder+  4237  4714  0 4月27 ?       00:31:19 postgres: hive1 hive1 10.98.131.138(58393) idle
clouder+  4238  4714  0 4月27 ?       00:31:21 postgres: hive1 hive1 10.98.131.138(58394) idle
clouder+  4246  4714  0 4月27 ?       00:31:28 postgres: hive1 hive1 10.98.131.137(52188) idle
clouder+  4247  4714  0 4月27 ?       00:30:58 postgres: hive1 hive1 10.98.131.137(52189) idle
clouder+  4255  4714  0 4月27 ?       00:28:43 postgres: hive1 hive1 10.98.131.136(58440) idle
clouder+  4256  4714  0 4月27 ?       00:28:44 postgres: hive1 hive1 10.98.131.136(58441) idle
clouder+  4714     1  0 4月25 ?       00:25:38 /usr/bin/postgres -D /var/lib/cloudera-scm-server-db/data -k /var/run/cloudera-scm-server/
clouder+  4715  4714  0 4月25 ?       00:00:00 postgres: logger process   
clouder+  4717  4714  0 4月25 ?       00:20:33 postgres: checkpointer process   
clouder+  4718  4714  0 4月25 ?       00:01:02 postgres: writer process   
clouder+  4719  4714  0 4月25 ?       00:02:26 postgres: wal writer process   
clouder+  4720  4714  0 4月25 ?       00:27:02 postgres: autovacuum launcher process   
clouder+  4721  4714  0 4月25 ?       01:17:42 postgres: stats collector process   
clouder+  6378  4714  0 4月27 ?       00:05:52 postgres: hue1 hue1 10.98.131.136(58589) idle
clouder+  6820  4714  0 9月26 ?       00:00:18 postgres: oozie_oozie_server1 oozie_oozie_server1 10.98.131.136(48578) idle
clouder+ 17078  3256  1 4月25 ?       2-08:45:11 /usr/java/jdk1.7.0_67-cloudera/bin/java -server -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Dmgmt.log.file=mgmt-cmf-mgmt-HOSTMONITOR-node136.log.out -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Dfirehose.schema.dir=/usr/share/cmf/schema -Dlibrary.leveldbjni.path=/run/cloudera-scm-agent/process/22-cloudera-mgmt-HOSTMONITOR -Xms1073741824 -Xmx1073741824 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/mgmt_mgmt-HOSTMONITOR-e088e1b54b32e1c2579fb48f905b08da_pid17078.hprof -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh -cp /run/cloudera-scm-agent/process/22-cloudera-mgmt-HOSTMONITOR:/usr/share/java/mysql-connector-java.jar:/usr/share/cmf/lib/postgresql-9.0-801.jdbc4.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/lib/*: com.cloudera.cmon.firehose.Main --pipeline-type HOST_MONITORING --mgmt-home /usr/share/cmf
clouder+ 17080  3256  0 4月25 ?       05:41:52 /usr/java/jdk1.7.0_67-cloudera/bin/java -server -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Dmgmt.log.file=mgmt-cmf-mgmt-ALERTPUBLISHER-node136.log.out -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Xms268435456 -Xmx268435456 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/mgmt_mgmt-ALERTPUBLISHER-e088e1b54b32e1c2579fb48f905b08da_pid17080.hprof -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh -cp /run/cloudera-scm-agent/process/23-cloudera-mgmt-ALERTPUBLISHER:/usr/share/java/mysql-connector-java.jar:/usr/share/cmf/lib/postgresql-9.0-801.jdbc4.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/lib/*: com.cloudera.enterprise.alertpublisher.AlertPublisher
clouder+ 17082  3256  9 4月25 ?       14-09:59:33 /usr/java/jdk1.7.0_67-cloudera/bin/java -server -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Dmgmt.log.file=mgmt-cmf-mgmt-SERVICEMONITOR-node136.log.out -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Dfirehose.schema.dir=/usr/share/cmf/schema -XX:PermSize=128m -Dsun.rmi.transport.tcp.handshakeTimeout=10000 -Dsun.rmi.transport.tcp.responseTimeout=10000 -Dlibrary.leveldbjni.path=/run/cloudera-scm-agent/process/24-cloudera-mgmt-SERVICEMONITOR -Xms1073741824 -Xmx1073741824 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/mgmt_mgmt-SERVICEMONITOR-e088e1b54b32e1c2579fb48f905b08da_pid17082.hprof -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh -cp /run/cloudera-scm-agent/process/24-cloudera-mgmt-SERVICEMONITOR:/usr/share/java/mysql-connector-java.jar:/usr/share/cmf/lib/postgresql-9.0-801.jdbc4.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/lib/*: com.cloudera.cmon.firehose.Main --pipeline-type SERVICE_MONITORING --mgmt-home /usr/share/cmf
clouder+ 17084  3256  1 4月25 ?       2-08:49:20 /usr/java/jdk1.7.0_67-cloudera/bin/java -server -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Dmgmt.log.file=mgmt-cmf-mgmt-EVENTSERVER-node136.log.out -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Xms1073741824 -Xmx1073741824 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/mgmt_mgmt-EVENTSERVER-e088e1b54b32e1c2579fb48f905b08da_pid17084.hprof -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh -cp /run/cloudera-scm-agent/process/25-cloudera-mgmt-EVENTSERVER:/usr/share/java/mysql-connector-java.jar:/usr/share/cmf/lib/postgresql-9.0-801.jdbc4.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/lib/*: com.cloudera.cmf.eventcatcher.server.EventCatcherService
clouder+ 20727  4714  0 4月26 ?       00:23:16 postgres: scm scm 127.0.0.1(41081) idle
clouder+ 20728  4714  0 4月26 ?       00:43:50 postgres: scm scm 127.0.0.1(41082) idle
clouder+ 20729  4714  0 4月26 ?       00:01:45 postgres: scm scm 127.0.0.1(41083) idle
clouder+ 25995  4714  0 8月31 ?       00:02:53 postgres: hive1 hive1 10.98.131.136(34763) idle
clouder+ 25996  4714  0 8月31 ?       00:02:52 postgres: hive1 hive1 10.98.131.136(34764) idle
clouder+ 27259  4714  0 4月26 ?       00:01:43 postgres: scm scm 127.0.0.1(32839) idle
clouder+ 27260  4714  0 4月26 ?       00:38:50 postgres: scm scm 127.0.0.1(32841) idle
clouder+ 27261  4714  0 4月26 ?       00:41:48 postgres: scm scm 127.0.0.1(32840) idle
clouder+ 27262  4714  0 4月26 ?       00:20:01 postgres: scm scm 127.0.0.1(32842) idle
clouder+ 27263  4714  0 4月26 ?       00:01:40 postgres: scm scm 127.0.0.1(32843) idle
clouder+ 27479  4714  0 4月26 ?       00:01:39 postgres: scm scm 127.0.0.1(33005) idle
clouder+ 27480  4714  0 4月26 ?       00:21:44 postgres: scm scm 127.0.0.1(33006) idle
clouder+ 27481  4714  0 4月26 ?       00:41:15 postgres: scm scm 127.0.0.1(33007) idle
clouder+ 27482  4714  0 4月26 ?       00:34:27 postgres: scm scm 127.0.0.1(33008) idle
clouder+ 27483  4714  0 4月26 ?       00:01:47 postgres: scm scm 127.0.0.1(33009) idle
clouder+ 27484  4714  0 4月26 ?       00:21:20 postgres: scm scm 127.0.0.1(33010) idle
clouder+ 27485  4714  0 4月26 ?       00:01:32 postgres: scm scm 127.0.0.1(33011) idle
clouder+ 27486  4714  0 4月26 ?       00:29:02 postgres: scm scm 127.0.0.1(33012) idle
clouder+ 27487  4714  0 4月26 ?       00:01:34 postgres: scm scm 127.0.0.1(33013) idle
clouder+ 27488  4714  0 4月26 ?       00:01:42 postgres: scm scm 127.0.0.1(33014) idle
clouder+ 27490  4714  0 4月26 ?       00:01:46 postgres: scm scm 127.0.0.1(33015) idle
clouder+ 27491  4714  0 4月26 ?       00:15:05 postgres: scm scm 127.0.0.1(33016) idle
clouder+ 27492  4714  0 4月26 ?       00:44:07 postgres: scm scm 127.0.0.1(33017) idle
clouder+ 27493  4714  0 4月26 ?       00:01:38 postgres: scm scm 127.0.0.1(33018) idle
clouder+ 27494  4714  0 4月26 ?       00:33:32 postgres: scm scm 127.0.0.1(33019) idle
clouder+ 32142  4714  0 4月26 ?       00:37:33 postgres: scm scm 127.0.0.1(34061) idle
clouder+ 32143  4714  0 4月26 ?       00:39:00 postgres: scm scm 127.0.0.1(34062) idle
clouder+ 32144  4714  0 4月26 ?       00:01:39 postgres: scm scm 127.0.0.1(34063) idle
root     36057 34737  0 13:18 pts/0    00:00:00 grep --color=auto postgres
clouder+ 37978  4714  0 9月26 ?       00:00:17 postgres: oozie_oozie_server1 oozie_oozie_server1 10.98.131.136(42450) idle
[root@node136 ~]# ps -ef|grep mysql
mysql     1629     1  0 4月25 ?       00:00:00 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
mysql     2216  1629  0 4月25 ?       01:25:56 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-file=/var/run/mariadb/mariadb.pid --socket=/var/lib/mysql/mysql.sock
clouder+ 17078  3256  1 4月25 ?       2-08:45:11 /usr/java/jdk1.7.0_67-cloudera/bin/java -server -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Dmgmt.log.file=mgmt-cmf-mgmt-HOSTMONITOR-node136.log.out -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Dfirehose.schema.dir=/usr/share/cmf/schema -Dlibrary.leveldbjni.path=/run/cloudera-scm-agent/process/22-cloudera-mgmt-HOSTMONITOR -Xms1073741824 -Xmx1073741824 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/mgmt_mgmt-HOSTMONITOR-e088e1b54b32e1c2579fb48f905b08da_pid17078.hprof -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh -cp /run/cloudera-scm-agent/process/22-cloudera-mgmt-HOSTMONITOR:/usr/share/java/mysql-connector-java.jar:/usr/share/cmf/lib/postgresql-9.0-801.jdbc4.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/lib/*: com.cloudera.cmon.firehose.Main --pipeline-type HOST_MONITORING --mgmt-home /usr/share/cmf
clouder+ 17080  3256  0 4月25 ?       05:41:52 /usr/java/jdk1.7.0_67-cloudera/bin/java -server -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Dmgmt.log.file=mgmt-cmf-mgmt-ALERTPUBLISHER-node136.log.out -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Xms268435456 -Xmx268435456 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/mgmt_mgmt-ALERTPUBLISHER-e088e1b54b32e1c2579fb48f905b08da_pid17080.hprof -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh -cp /run/cloudera-scm-agent/process/23-cloudera-mgmt-ALERTPUBLISHER:/usr/share/java/mysq-connector-java.jar:/usr/share/cmf/lib/postgresql-9.0-801.jdbc4.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/lib/*: com.cloudera.enterprise.alertpublisher.AlertPublisher
clouder+ 17082  3256  9 4月25 ?       14-09:59:33 /usr/java/jdk1.7.0_67-cloudera/bin/java -server -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Dmgmt.log.file=mgmt-cmf-mgmt-SERVICEMONITOR-node136.log.out -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Dfirehose.schema.dir=/usr/share/cmf/schema -XX:PermSize=128m -Dsun.rmi.transport.tcp.handshakeTimeout=10000 -Dsun.rmi.transport.tcp.responseTimeout=10000 -Dlibrary.leveldbjni.path=/run/cloudera-scm-agent/process/24-cloudera-mgmt-SERVICEMONITOR -Xms1073741824 -Xmx1073741824 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/mgmt_mgmt-SERVICEMONITOR-e088e1b54b32e1c2579fb48f905b08da_pid17082.hprof -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh -cp /run/cloudera-scm-agent/process/24-cloudera-mgmt-SERVICEMONITOR:/usr/share/java/mysql-connector-java.jar:/usr/share/cmf/lib/postgresql-9.0-801.jdbc4.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/lib/*: com.cloudera.cmon.firehose.Main --pipeline-type SERVICE_MONITORING --mgmt-home /usr/share/cmf
clouder+ 17084  3256  1 4月25 ?       2-08:49:20 /usr/java/jdk1.7.0_67-cloudera/bin/java -server -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Dmgmt.log.file=mgmt-cmf-mgmt-EVENTSERVER-node136.log.out -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Xms1073741824 -Xmx1073741824 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/mgmt_mgmt-EVENTSERVER-e088e1b54b32e1c2579fb48f905b08da_pid17084.hprof -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh -cp /run/cloudera-scm-agent/process/25-cloudera-mgmt-EVENTSERVER:/usr/share/java/mysql-connector-java.jar:/usr/share/cmf/lib/postgresql-9.0-801.jdbc4.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/lib/*: com.cloudera.cmf.eventcatcher.server.EventCatcherService
clouder+ 27180 27177  2 4月26 ?       3-04:59:42 /usr/java/jdk1.7.0_67-cloudera/bin/java -cp .:lib/*:/usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar -server -Dlog4j.configuration=file:/etc/cloudera-scm-server/log4j.properties -Dfile.encoding=UTF-8 -Dcmf.root.logger=INFO,LOGFILE -Dcmf.log.dir=/var/log/cloudera-scm-server -Dcmf.log.file=cloudera-scm-server.log -Dcmf.jetty.threshhold=WARN -Dcmf.schema.dir=/usr/share/cmf/schema -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Dpython.home=/usr/share/cmf/python -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+HeapDumpOnOutOfMemoryError -Xmx2G -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -XX:OnOutOfMemoryError=kill -9 %p com.cloudera.server.cmf.Main
root     36652 34737  0 13:18 pts/0    00:00:00 grep --color=auto mysql

从节点状态如下:

[root@node140 ~]# /etc/init.d/cloudera-scm-agent status
● cloudera-scm-agent.service - LSB: Cloudera SCM Agent
   Loaded: loaded (/etc/rc.d/init.d/cloudera-scm-agent; bad; vendor preset: disabled)
   Active: active (exited) since 四 2018-04-26 11:48:11 CST; 5 months 1 days ago
     Docs: man:systemd-sysv-generator(8)
   Memory: 0B

4月 26 11:48:10 node140 systemd[1]: Starting LSB: Cloudera SCM Agent...
4月 26 11:48:11 node140 su[5678]: (to root) root on none
4月 26 11:48:11 node140 cloudera-scm-agent[5662]: Starting cloudera-scm-agent: [  确定  ]
4月 26 11:48:11 node140 systemd[1]: Started LSB: Cloudera SCM Agent.
[root@node140 ~]# /etc/init.d/cloudera-scm-server status 
● cloudera-scm-server.service - LSB: Cloudera SCM Server
   Loaded: loaded (/etc/rc.d/init.d/cloudera-scm-server; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since 四 2018-04-26 02:38:39 CST; 5 months 2 days ago
     Docs: man:systemd-sysv-generator(8)

4月 26 02:38:39 node140 systemd[1]: Unit cloudera-scm-server.service entered failed state.
4月 26 02:38:39 node140 systemd[1]: cloudera-scm-server.service failed.
4月 26 17:29:18 node140 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:8] Failed t...ument
4月 26 17:29:19 node140 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:13] Failed ...ument
4月 26 17:29:23 node140 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:13] Failed ...ument
4月 26 17:29:51 node140 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:13] Failed ...ument
4月 26 17:30:10 node140 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:13] Failed ...ument
4月 26 17:30:47 node140 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:13] Failed ...ument
8月 16 15:04:50 node140 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:13] Failed ...ument
8月 16 15:24:23 node140 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:13] Failed ...ument
Hint: Some lines were ellipsized, use -l to show in full.
[root@node140 ~]# ls
1                               cncert-api.tar.part.-verboseae                setup_cloudera_env.sh
anaconda-ks.cfg                 dns.json                                      spark_jobs.sql
bak                             dns.json.tar.gz                               sqljob.sql
be.tar                          dns,whois脚本                                 tmp
cd_section9                     docker-ce-18.03.1.ce-1.el7.centos.x86_64.rpm  whois.json
CentOS-7.2-x86_64-DVD-1511.iso  Hadoop                                        whois.json.tar.gz
cncert-api.tar.part.-verboseaa  important                                     write_fstab.sh
cncert-api.tar.part.-verboseab  insight_sources.sql                           yum_bak
cncert-api.tar.part.-verboseac  install.sql                                   zhoukang
cncert-api.tar.part.-verbosead  pigz-2.3.4-1.el7.x86_64.rpm
您在 /var/spool/mail/root 中有新邮件
[root@node140 ~]# ps -ef|grep mysql
root      1774   502  0 13:27 pts/0    00:00:00 grep --color=auto mysql
yarn      9315  9312  0 9月19 ?       00:00:00 /bin/bash -c LD_LIBRARY_PATH=/opt/cloudera/parcels/CDH-5.14.2-1.cdh5.14.2.p0.3/lib/hadoop/../../../CDH-5.14.2-1.cdh5.14.2.p0.3/lib/hadoop/lib/native::/opt/cloudera/parcels/CDH-5.14.2-1.cdh5.14.2.p0.3/lib/hadoop/lib/native /usr/java/jdk1.8.0_172-amd64/bin/java -server -Xmx6144m -Djava.io.tmpdir=/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/tmp '-Dspark.driver.port=56069' '-Dspark.authenticate.enableSaslEncryption=false' '-Dspark.authenticate=false' '-Dspark.shuffle.service.port=7337' '-Dspark.network.timeout=100' -Dspark.yarn.app.container.log.dir=/data/disk01/yarn/container-logs/application_1524801901186_0192/container_1524801901186_0192_01_000002 -XX:OnOutOfMemoryError='kill %p' org.apache.spark.executor.CoarseGrainedExecutorBackend --driver-url spark://CoarseGrainedScheduler@node136:56069 --executor-id 1 --hostname node140 --cores 2 --app-id application_1524801901186_0192 --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/__app__.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/kafka-clients-0.10.0.0.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/log4j2.xml --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/spark-sql-kafka-0-10_2.11-2.3.0.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/xmatrix-manager-1.2.0.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/elasticsearch-spark-20_2.11-6.3.0.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/mysql-connector-java-5.1.22.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/tispark-core-1.1-SNAPSHOT-jar-with-dependencies.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/antiy-udf-1.0.0.jar 1>/data/disk01/yarn/container-logs/application_1524801901186_0192/container_1524801901186_0192_01_000002/stdout 2>/data/disk01/yarn/container-logs/application_1524801901186_0192/container_1524801901186_0192_01_000002/stderr
yarn      9798  9315 23 9月19 ?       1-20:03:42 /usr/java/jdk1.8.0_172-amd64/bin/java -server -Xmx6144m -Djava.io.tmpdir=/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/tmp -Dspark.driver.port=56069 -Dspark.authenticate.enableSaslEncryption=false -Dspark.authenticate=false -Dspark.shuffle.service.port=7337 -Dspark.network.timeout=100 -Dspark.yarn.app.container.log.dir=/data/disk01/yarn/container-logs/application_1524801901186_0192/container_1524801901186_0192_01_000002 -XX:OnOutOfMemoryError=kill %p org.apache.spark.executor.CoarseGrainedExecutorBackend --driver-url spark://CoarseGrainedScheduler@node136:56069 --executor-id 1 --hostname node140 --cores 2 --app-id application_1524801901186_0192 --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/__app__.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/kafka-clients-0.10.0.0.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/log4j2.xml --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/spark-sql-kafka-0-10_2.11-2.3.0.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/xmatrix-manager-1.2.0.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/elasticsearch-spark-20_2.11-6.3.0.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/mysql-connector-java-5.1.22.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/tispark-core-1.1-SNAPSHOT-jar-with-dependencies.jar --user-class-path file:/data/disk02/yarn/nm/usercache/spark2/appcache/application_1524801901186_0192/container_1524801901186_0192_01_000002/antiy-udf-1.0.0.jar
27       24040 23907  4 8月16 ?       1-18:34:52 mysqld --datadir=/data/mysql --user=mysql
systemd+ 24796 24780  0 8月16 ?       00:37:11 mysqld
[root@node140 ~]# ps -ef|grep postgres
systemd+   476 23463  0 13:25 ?        00:00:00 postgres: kong kong 172.18.0.8(37012) idle
systemd+  1139 23463  0 13:26 ?        00:00:00 postgres: kong kong 172.18.0.8(37124) idle
systemd+  1142 23463  0 13:26 ?        00:00:00 postgres: kong kong 172.18.0.8(37127) idle
systemd+  1291 23463  0 13:26 ?        00:00:00 postgres: kong kong 172.18.0.8(37185) idle
systemd+  1292 23463  0 13:26 ?        00:00:00 postgres: kong kong 172.18.0.8(37186) idle
systemd+  1293 23463  0 13:26 ?        00:00:00 postgres: kong kong 172.18.0.8(37187) idle
systemd+  1360 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37193) idle
systemd+  1520 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37208) idle
systemd+  1572 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37233) idle
systemd+  1573 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37234) idle
systemd+  1682 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37251) idle
systemd+  1683 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37252) idle
systemd+  1684 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37253) idle
systemd+  1685 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37254) idle
systemd+  1686 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37255) idle
systemd+  1687 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37256) idle
systemd+  1688 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37258) idle
systemd+  1692 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37260) idle
systemd+  1693 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37262) idle
systemd+  1695 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37264) idle
systemd+  1697 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37265) idle
systemd+  1699 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37268) idle
systemd+  1715 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37277) idle
systemd+  1717 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37278) idle
systemd+  1720 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37282) idle
systemd+  1721 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37283) idle
systemd+  1722 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37284) idle
systemd+  1777 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37291) idle
systemd+  1778 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37292) idle
systemd+  1779 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37293) idle
systemd+  1780 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37294) idle
systemd+  1781 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37295) idle
systemd+  1782 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37296) idle
systemd+  1783 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37297) idle
systemd+  1784 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37298) idle
systemd+  1786 23463  0 13:27 ?        00:00:00 postgres: kong kong 172.18.0.8(37301) idle
root      1790   502  0 13:27 pts/0    00:00:00 grep --color=auto postgres
clouder+  3416     1  0 4月25 ?       00:02:23 /usr/bin/postgres -D /var/lib/cloudera-scm-server-db/data -k /var/run/cloudera-scm-server/
clouder+  3417  3416  0 4月25 ?       00:00:00 postgres: logger process   
clouder+  3419  3416  0 4月25 ?       00:00:03 postgres: checkpointer process   
clouder+  3420  3416  0 4月25 ?       00:00:59 postgres: writer process   
clouder+  3421  3416  0 4月25 ?       00:01:08 postgres: wal writer process   
clouder+  3422  3416  0 4月25 ?       00:01:34 postgres: autovacuum launcher process   
clouder+  3423  3416  0 4月25 ?       00:02:24 postgres: stats collector process   
systemd+ 23463 23447  0 8月16 ?       00:21:17 postgres
systemd+ 23623 23463  0 8月16 ?       00:00:00 postgres: checkpointer process  
systemd+ 23624 23463  0 8月16 ?       00:00:17 postgres: writer process  
systemd+ 23625 23463  0 8月16 ?       00:00:18 postgres: wal writer process  
systemd+ 23626 23463  0 8月16 ?       00:00:26 postgres: autovacuum launcher process  
systemd+ 23627 23463  0 8月16 ?       00:04:11 postgres: stats collector process  
systemd+ 40234 23463  0 13:23 ?        00:00:00 postgres: kong kong 172.18.0.8(36826) idle
systemd+ 40306 23463  0 13:24 ?        00:00:00 postgres: kong kong 172.18.0.8(36838) idle
systemd+ 40824 23463  0 13:24 ?        00:00:00 postgres: kong kong 172.18.0.8(36937) idle
systemd+ 40829 23463  0 13:24 ?        00:00:00 postgres: kong kong 172.18.0.8(36941) idle

参考:
https://blog.csdn.net/lxf20054658/article/details/73695469
https://blog.csdn.net/chenhai201/article/details/78856007

故障处理:
https://blog.csdn.net/u011031430/article/details/74057601
https://cloud.tencent.com/developer/article/1079123

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值