03-30-2017 01:46 PM
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
com.cloudera.parcel.ParcelException: Cluster <b>cluster</b> has no member hosts. Add hosts to the cluster and then try again.
Screenshot of where it hangs:
Back at the Dashboard
The hosts have the agent installed and appear in good condition:
Thanks in advance.
Solved! Go to Solution.
03-31-2017 08:01 AM
Thank you for reaching out to us, in order to assist you we would need to see additional log information from Cloudera Manager. The error you have referenced indicates that no host have been added to the cluster you are attempting to install parcels to. Based on what is here at this moment this does not appear to be a bug or a change in our software behavior.
In addition to that the error you provided has a differeing cluster name than the ones you provided in your screenshots. We also note that your screenshots show 'Cluster 1' as having CDH 5.0.0 deployed via packages and not via parcels. The All Host page does not show us which host are presently assigned to a specific cluster without filtering.
If you have added host to Cluster 1 or another cluster please use the 'Cluster' filter on the side of the All Host page so that we can see which host are assigned to that cluster. Please confirm the cluster name, CDH release, Packaging method, and any previous deployment steps you have taken.
04-17-2017 12:03 PM
Thank you for working with me via messages to resolve my issue.
As you stated in your message to me, FQDN resolution was the cause of my problem. Since we're not using a DNS solution for our environment, once I entered the cluster hosts FQDNs into the CM's /etc/hosts, the parcels no longer hung at distribution and the installation was able to continue.