Member since
05-22-2017
15
Posts
6
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
6571 | 02-21-2018 10:22 PM |
02-21-2018
10:22 PM
as a quick solution, added auto recovery code to our tool, i.e. check datanode role status after cluster startup completion and run start command for each stopped datanode role. goes like this Welcome to
_ __
| | /| / /______ ____ ___
| |/ |/ / __/ _ `/ _ \(_-<
|__/|__/_/ \_,_/ .__/___/ version 1.0.2
/_/
starting hdfs-DATANODE-ac7041aa53e984590b7d2e27a66ae6ed
starting hdfs-DATANODE-c3a2e16a1c264acbf2b3a8cd036c8abd
starting hdfs-DATANODE-59269ad5f41a6f45c24d9971f1e45660
starting hdfs-DATANODE-47a0b595206a0616ff011606dff76d0f
waiting 30 sec.
HDFS health checks [0]
+-----------------------------------+---------------+
| NAME | SUMMARY |
+-----------------------------------+---------------+
|HDFS_BLOCKS_WITH_CORRUPT_REPLICAS | GOOD |
|HDFS_CANARY_HEALTH | BAD |
|HDFS_DATA_NODES_HEALTHY | CONCERNING |
|HDFS_FAILOVER_CONTROLLERS_HEALTHY | GOOD |
|HDFS_FREE_SPACE_REMAINING | GOOD |
|HDFS_HA_NAMENODE_HEALTH | GOOD |
|HDFS_MISSING_BLOCKS | GOOD |
|HDFS_UNDER_REPLICATED_BLOCKS | GOOD |
+-----------------------------------+---------------+
... View more
06-02-2017
07:23 AM
Thanks a lot. I have encountered the same problem while upgrading from CDH5.10.0 to CDH5.11.0. Management services (including Navigator) where not able to start. I have followed your instructions and after restart of cloudera agent, the mgmt services were able to start.
... View more