Support Questions
Find answers, ask questions, and share your expertise
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Who agreed with this topic

Cloudera Manager Hangs When Installing Parcels

New Contributor


Been working with Cloudera for about 2 years now and up until recently, when the Cloudera Express 5.9 version was released, I had no issue adding a cluster. Starting with 5.9, when adding a cluster, I can find and select the hosts, parcels, install the CM agent and get a good status on a heartbeat. When the Installing Selected Parcels step comes in, I show 100% downloaded, but 0/0 in Distributed, Unpacked, and Activated. The issue exists regardless of which parcel or how many types I choose to install. My logs show the new cluster has no member hosts. I then have to open a new window, add the hosts to the cluster, distribute and upgrade CDH to get the parcels to distribute, unpack, and activate.


I thought it may have been a bug within the Cloudera Express 5.9.1, so I stood a new server up and installed the trial version of Enterprise Data Hub 5.10.1 only to have the same result. I can't find Cloudera reporting this as a known issue or any other instances of this exact problem. Can someone please help?


My configuration is an AWS environment with a single RHEL 6.8 (CE 5.9.1) and RHEL 7.3 (EDH 5.10.1) server; I am not running single-user mode.


Below is from the Enterprise Data Hub trial version 5.10.1, however the same errors and issues exist in the Express 5.9.1 version.



An excerpt of the log:


2017-03-30 16:13:48,639 WARN ParcelUpdateService:com.cloudera.parcel.components.ParcelInstallerImpl: Error while installing parcel
com.cloudera.parcel.ParcelException: Cluster <b>cluster</b> has no member hosts. Add hosts to the cluster and then try again.
        at com.cloudera.parcel.components.ParcelManagerImpl.distribute(
        at com.cloudera.parcel.components.ParcelInstallerImpl.handleJob(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$



Screenshot of where it hangs:



Back at the Dashboard


The hosts have the agent installed and appear in good condition:



Thanks in advance.


Who agreed with this topic