logo
down
shadow

restart a CDH5 cluster on EC2 saved as AMI


restart a CDH5 cluster on EC2 saved as AMI

By : Libao He
Date : November 16 2020, 06:23 AM
With these it helps The reason this seems to be failing are the host names. When assigning a static private IP to an instance the hostname changes to ip-xx-xx-xx-xx.
Editing the hosts file didn't seem to help.
code :


Share : facebook icon twitter icon
DataNode automatically getting restarted in the CDH5 cluster

DataNode automatically getting restarted in the CDH5 cluster


By : user2349593
Date : March 29 2020, 07:55 AM
fixed the issue. Will look into that further As the pid of datanode has been changed, I don't think it is a behavior of datanode. If you are managing your cluster using Cloudera Manager, there is an option for restarting datanode daemon if it fails(Automatically Restart Process). This option will be set by default. When the datanode process gets failed or killed, As Automatic restart option is set Cloudera Scm agent will start the the datanode daemon.
For Automatic restart option : Choose HDFS services -> go to Configuration section -> Search for automatic restart.
My cdh5.2 cluster get FileNotFoundException when running hbase MR jobs

My cdh5.2 cluster get FileNotFoundException when running hbase MR jobs


By : user2860810
Date : March 29 2020, 07:55 AM
To fix the issue you can do So, The problem was environment issue: When I added the below jars into /usr/lib/hadoop/lib. all worked fine
code :
hbase-client-0.98.6-cdh5.2.1.jar
hbase-common-0.98.6-cdh5.2.1.jar
hbase-protocol-0.98.6-cdh5.2.1.jar
hbase-server-0.98.6-cdh5.2.1.jar
hbase-prefix-tree-0.98.6-cdh5.2.1.jar
hadoop-core-2.5.0-mr1-cdh5.2.1.jar
htrace-core-2.04.jar
>> rpm -qa | grep cdh
zookeeper-3.4.5+cdh5.2.1+84-1.cdh5.2.1.p0.13.el6.x86_64
hadoop-2.5.0+cdh5.2.1+578-1.cdh5.2.1.p0.14.el6.x86_64
hadoop-0.20-mapreduce-2.5.0+cdh5.2.1+578-1.cdh5.2.1.p0.14.el6.x86_64
hbase-regionserver-0.98.6+cdh5.2.1+64-1.cdh5.2.1.p0.9.el6.x86_64
cloudera-cdh-5-0.x86_64
bigtop-utils-0.7.0+cdh5.2.1+0-1.cdh5.2.1.p0.13.el6.noarch
bigtop-jsvc-0.6.0+cdh5.2.1+578-1.cdh5.2.1.p0.13.el6.x86_64
parquet-1.5.0+cdh5.2.1+38-1.cdh5.2.1.p0.12.el6.noarch
hadoop-hdfs-2.5.0+cdh5.2.1+578-1.cdh5.2.1.p0.14.el6.x86_64
hadoop-mapreduce-2.5.0+cdh5.2.1+578-1.cdh5.2.1.p0.14.el6.x86_64
hadoop-0.20-mapreduce-tasktracker-2.5.0+cdh5.2.1+578-1.cdh5.2.1.p0.14.el6.x86_64
hbase-0.98.6+cdh5.2.1+64-1.cdh5.2.1.p0.9.el6.x86_64
avro-libs-1.7.6+cdh5.2.1+69-1.cdh5.2.1.p0.13.el6.noarch
parquet-format-2.1.0+cdh5.2.1+6-1.cdh5.2.1.p0.14.el6.noarch
hadoop-yarn-2.5.0+cdh5.2.1+578-1.cdh5.2.1.p0.14.el6.x86_64
hadoop-hdfs-datanode-2.5.0+cdh5.2.1+578-1.cdh5.2.1.p0.14.el6.x86_64
Jgroups cluster breaks on restart of individual cluster members

Jgroups cluster breaks on restart of individual cluster members


By : Kateryna Rybalko
Date : March 29 2020, 07:55 AM
I wish this helpful for you How do you restart your nodes? By killing them, or by a graceful shutdown (= cluster leave)? A few comments to your config:
How can i get the version info of flume in use of my cluster(cloudera CDH5.5.1)?

How can i get the version info of flume in use of my cluster(cloudera CDH5.5.1)?


By : Schusch
Date : March 29 2020, 07:55 AM
Any of those help You can issue the command flume-ng version on the/any host to get the version.
stop cloudera CDH5 cluster command line

stop cloudera CDH5 cluster command line


By : alpha2theomega
Date : March 29 2020, 07:55 AM
I wish this help you If you stop the scloudera scm server/agent you will not stop the services. In order to do so:
You need to make a REST request with curl to your cloudera scm server.
Related Posts Related Posts :
shadow
Privacy Policy - Terms - Contact Us © ourworld-yourmove.org