Cloudera Community

Support Questions

Find answers, ask questions, and share your expertise
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search

Docker-compose Create Hadoop Cluster

Labels:
avatar
author-rank hsuan
Explorer

Created ‎08-18-2021 07:43 PM

I use docker-compose to create hadoop cluster with HA. But it always show the problem. Below are the response, set-up file, and the sequence of start-up. Thank you for any answer. 

 

2021-08-19 09:08:15,718 INFO util.GSet: Computing capacity for map NameNodeRetryCache
2021-08-19 09:08:15,718 INFO util.GSet: VM type       = 64-bit
2021-08-19 09:08:15,718 INFO util.GSet: 0.029999999329447746% max memory 14.0 GB = 4.3 MB
2021-08-19 09:08:15,718 INFO util.GSet: capacity      = 2^19 = 524288 entries
2021-08-19 09:08:17,009 INFO ipc.Client: Retrying connect to server: journalnode2/172.18.0.5:8485. Already tried 0 time(s); retry polic
y is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:17,009 INFO ipc.Client: Retrying connect to server: journalnode3/172.18.0.11:8485. Already tried 0 time(s); retry poli
cy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:17,009 INFO ipc.Client: Retrying connect to server: journalnode1/172.18.0.12:8485. Already tried 0 time(s); retry poli
cy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:18,010 INFO ipc.Client: Retrying connect to server: journalnode2/172.18.0.5:8485. Already tried 1 time(s); retry polic
y is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:18,010 INFO ipc.Client: Retrying connect to server: journalnode1/172.18.0.12:8485. Already tried 1 time(s); retry poli
cy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:18,010 INFO ipc.Client: Retrying connect to server: journalnode3/172.18.0.11:8485. Already tried 1 time(s); retry poli
cy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:19,011 INFO ipc.Client: Retrying connect to server: journalnode3/172.18.0.11:8485. Already tried 2 time(s); retry poli
cy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:19,011 INFO ipc.Client: Retrying connect to server: journalnode2/172.18.0.5:8485. Already tried 2 time(s); retry polic
y is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:19,011 INFO ipc.Client: Retrying connect to server: journalnode1/172.18.0.12:8485. Already tried 2 time(s); retry poli
cy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:20,013 INFO ipc.Client: Retrying connect to server: journalnode2/172.18.0.5:8485. Already tried 3 time(s); retry polic
y is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2021-08-19 09:08:20,013 INFO ipc.Client: Retrying connect to server: journalnode1/172.18.0.12:8485. Already tried 3 time(s); retry poli

 

 

core-site.xml

 

<configuration>
  <property>
      <name>hadoop.tmp.dir</name>
      <value>/usr/local/hadoop/data</value>
      <description>Temporary Directory.</description>
  </property>
  <property>
      <name>fs.defaultFS</name>
      <value>hdfs://nncluster</value>
      <description>Use HDFS as file storage engine</description>
  </property>
  <property>
      <name>ha.zookeeper.quorum</name>
      <value>journalnode1:2181,journalnode2:2181,journalnode3:2181</value>
  </property>
  <property>
      <name>dfs.nameservices</name>
      <value>nncluster</value>
  </property>
</configuration>

 

 

hdfs-site.xml

 

<configuration>
  <property>
     <name>dfs.nameservices</name>
     <value>nncluster</value>
   </property>
   <property>
     <name>dfs.ha.namenodes.nncluster</name>
     <value>nn1,nn2</value>
   </property>
   <property>
     <name>dfs.namenode.rpc-address.nncluster.nn1</name>
     <value>active-nn:8020</value>
   </property>
   <property>
     <name>dfs.namenode.http-address.nncluster.nn1</name>
     <value>active-nn:9870</value>
   </property>
   <property>
     <name>dfs.namenode.rpc-address.nncluster.nn2</name>
     <value>standby-nn:8020</value>
   </property>
   <property>
     <name>dfs.namenode.http-address.nncluster.nn2</name>
     <value>standby-nn:9870</value>
   </property>
   <property>
     <name>ha.zookeeper.quorum</name>
     <value>journalnode1:2181,journalnode2:2181,journalnode3:2181</value>
   </property>
   <property>
     <name>dfs.namenode.shared.edits.dir</name>
     <value>qjournal://journalnode1:8485;journalnode2:8485;journalnode3:8485/nncluster</value>
   </property>
   <property>
     <name>dfs.journalnode.edits.dir</name>
     <value>/usr/local/hadoop/data/journalnode</value>
   </property>
   <property>
     <name>dfs.namenode.name.dir</name>
     <value>/usr/local/hadoop/data/namenode</value>
   </property>
   <property>
      <name>dfs.datanode.data.dir</name>
      <value>/usr/local/hadoop/data/datanode</value>
   </property>
   <!--
   <property>
     <name>dfs.ha.fencing.methods</name>
     <value>sshfence</value>
   </property>
   <property>
     <name>dfs.ha.fencing.ssh.private-key-files</name>
     <value>/home/hadoop/.ssh/id_dsa</value>
   </property>
   -->
   <property>
     <name>dfs.ha.fencing.methods</name>
     <value>shell(/bin/true)</value>
   </property>
   <property>
     <name>dfs.client.failover.proxy.provider.nncluster</name>
     <value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider</value>
   </property>
   <property>
     <name>dfs.ha.automatic-failover.enabled</name>
     <value>true</value>
   </property>
</configuration>

 

 

mapred-site.xml

 

<configuration>
  <property>
      <name>yarn.app.mapreduce.am.resource.vcores</name>
      <value>3</value>
  </property>
  <property>
      <name>yarn.app.mapreduce.am.resource.memory-mb</name>
      <value>6656</value>
  </property>
  <property>
      <name>yarn.app.mapreduce.am.command-opts</name>
      <value>-Xmx5324m</value>
  </property>
  <!--
  <property>
      <name>mapreduce.job.heap.memory-mb.ratio</name>
      <value>0.8</value>
  </property>
  -->
  <property>
      <name>mapreduce.map.resource.vcores</name>
      <value>3</value>
  </property>
  <property>
      <name>mapreduce.map.resource.memory-mb</name>
      <value>6656</value>
  </property>
  <property>
      <name>mapreduce.map.java.opts</name>
      <value>-Xmx5324m</value>
  </property>
  <property>
      <name>mapreduce.task.io.sort.mb</name>
      <value>1331</value>
  </property>
  <property>
      <name>mapreduce.reduce.resource.vcores</name>
      <value>3</value>
  </property>
  <property>
      <name>mapreduce.reduce.resource.memory-mb</name>
      <value>6656</value>
  </property>
  <property>
      <name>mapreduce.reduce.java.opts</name>
      <value>-Xmx5324m</value>
  </property>
  <property>
     <name>mapreduce.framework.name</name>
     <value>yarn</value>
  </property>
  <property>
     <name>mapreduce.jobhistory.address</name>
     <value>historysever:10020</value>
  </property>
  <property>
     <name>mapreduce.jobhistory.webapp.address</name>
     <value>historysever:19888</value>
  </property>
</configuration>

 

 

yarn-site.xml

 

<configuration>
  <!-- Site specific YARN configuration properties -->
  <property>
    <name>yarn.nodemanager.aux-services</name>
    <value>mapreduce_shuffle</value>
  </property>
  <property>
    <name>yarn.nodemanager.env-whitelist</name>
    <value>JAVA_HOME,HADOOP_COMMON_HOME,HADOOP_HDFS_HOME,HADOOP_CONF_DIR,CLASSPATH_PREPEND_DISTCACHE,HADOOP_YARN_HOME,HADOOP_MAPRED_HOME</value>
  </property>
  <property>
    <name>yarn.nodemanager.resource.cpu-vcores</name>
    <value>3</value>
  </property>
  <property>
    <name>yarn.nodemanager.resource.memory-mb</name>
    <value>20480</value>
  </property>
  <property>
    <name>yarn.scheduler.maximum-allocation-vcores</name>
    <value>3</value>
  </property>
  <property>
    <name>yarn.scheduler.minimum-allocation-mb</name>
    <value>1024</value>
  </property>
  <property>
    <name>yarn.scheduler.maximum-allocation-mb</name>
    <value>20480</value>
  </property>
  <property>
    <name>yarn.resource-types.memory-mb.increment-allocation</name>
    <value>512</value>
  </property>
  <property>
    <name>yarn.resourcemanager.ha.enabled</name>
    <value>true</value>
  </property>
  <property>
    <name>yarn.resourcemanager.cluster-id</name>
    <value>rmcluster</value>
  </property>
  <property>
    <name>yarn.resourcemanager.ha.rm-ids</name>
    <value>rm1,rm2</value>
  </property>
  <property>
  <name>yarn.resourcemanager.hostname.rm1</name>
    <value>active-rm</value>
  </property>
  <property>
    <name>yarn.resourcemanager.hostname.rm2</name>
    <value>standby-rm</value>
  </property>
  <property>
    <name>yarn.resourcemanager.webapp.address.rm1</name>
    <value>active-rm:8088</value>
  </property>
  <property>
    <name>yarn.resourcemanager.webapp.address.rm2</name>
    <value>standby-rm:8088</value>
  </property>
  <property>
    <name>yarn.resourcemanager.recovery.enabled</name>
    <value>true</value>
  </property>
  <property>
    <name>yarn.resourcemanager.store.class</name>
    <value>org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore</value>
  </property>
  <property>
    <name>yarn.resourcemanager.zk-address</name>
    <value>journalnode1:2181,journalnode2:2181,journalnode3:2181</value>
  </property>
<!-- <property> <name>yarn.nodemanager.resource.detect-hardware-capabilities</name> <value>true</value> </property> <property> <name>yarn.nodemanager.vmem-pmem-ratio</name> <value>4.2</value> </property> -->
  </configuration>

 

 

the sequence of start-up

 

# [Zookeeper start]
docker exec -it journalnode1 /bin/bash -c  "/usr/local/zookeeper/bin/zkServer.sh start" && docker exec -it journalnode2 /bin/bash -c  "/usr/local/zookeeper/bin/zkServer.sh start" && docker exec -it journalnode3 /bin/bash -c  "/usr/local/zookeeper/bin/zkServer.sh start"

# [Journal start]
docker exec -it journalnode1 /bin/bash -c  "/usr/local/hadoop/bin/hdfs --daemon start journalnode" && docker exec -it journalnode2 /bin/bash -c  "/usr/local/hadoop/bin/hdfs --daemon start journalnode" && docker exec -it journalnode3 /bin/bash -c  "/usr/local/hadoop/bin/hdfs --daemon start journalnode"

# [NN format]
docker exec -it active-nn /bin/bash -c "/usr/local/hadoop/bin/hdfs namenode -format"

# [NN zookeeper start]
docker exec -it active-nn /bin/bash -c  "/usr/local/hadoop/bin/hdfs zkfc -formatZK"

docker exec -it active-nn /bin/bash -c "/usr/local/hadoop/sbin/start-dfs.sh"

# [Standby get data]
docker exec -it standby-nn /bin/bash -c "/usr/local/hadoop/bin/hdfs namenode -bootstrapStandby"

docker exec -it standby-nn /bin/bash -c "/usr/local/hadoop/bin/hdfs --daemon start namenode"

# [NN && RM && HS start]
docker exec -it active-nn /bin/bash -c "/usr/local/hadoop/sbin/start-dfs.sh"
docker exec -it active-rm /bin/bash -c "/usr/local/hadoop/sbin/start-yarn.sh"
docker exec -it historyserver /bin/bash -c "/usr/local/hadoop/bin/mapred --daemon start historyserver"

 

 

The error response show when I exec NN format, docker exec -it active-nn /bin/bash -c "/usr/local/hadoop/bin/hdfs namenode -format".

 

 

All these codes are in the https://github.com/KarenPHS/HadoopCluster.

2,072 Views
0 Kudos
0 REPLIES 0
Announcements
What's New @ Cloudera
Cloudera Data Engineering 1.23: Access Spark from Your Favor...
What's New @ Cloudera
HBase REST server scaling support is Generally Available
What's New @ Cloudera
New CLI option in the update-database command
What's New @ Cloudera
New Action menu item in the Cloudera Operational Database UI
What's New @ Cloudera
Get the list of supported instance types in the Cloudera Ope...
View More Announcements