@wert_1311 ,   Any luck with this? Found the root cause?   André ... View more

Hi @Koffi    Maybe this could be of some use - https://community.cloudera.com/t5/Support-Questions/CDH5-2-yarn-Error-starting-yarn-nodemanagers/td-p/21700  ... View more

You can find the error message 'Index build failed for service hdfs' in RM log. This issue is caused by exceptional ' /var/lib/cloudera-scm-headlamp/' where the Reports Manager role is configured to run.   step 1: stop CMS Reports Manager role   step 2: RUN THIS ON THE HOST WHERE RM ROLE RUNS sudo rm -rf /var/lib/cloudera-scm-headlamp/*   step 3: start CMS Reports Manager role (will rebuild the headlamp dir)   Done.   You can now use CM> HDFS> File Browser. ... View more

Hi Team,   I believe your issue has not been resolved till now hence i am pointing toward a direction where you need to look..!!   if you TS is taking 3-4 hours it means there is a massive overload on them, Please check the scheme/scala from kudu runbook   https://kudu.apache.org/docs/scaling_guide.html   Points need to check:   1) Please check how many Tablet per TS you have, we don't recommend more than 2K per TS post replication 2) Does your master WAL and Data directory is on same disk, as its not recommended too 3) How many data directory you have per TS, keep from 3-12..!! 4) Please run your kudu cluster ksck <master_addrss>  command and check if your cluster is in healthy state..!!     Thanks..!! ... View more

This seems a Connection time out to the name node so you may want to check if there is any Network issue or something else going on with CM's help. That should give you some clue. ... View more

@wert_1311, has @kingpin's reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  ... View more