Parcel not distributed but have active state ACTIVATING

[#1]

Parcel not distributed but have active state ACTIVATING

[#2]

I'll move this question to the right forum. Can you please post a screenshot of the issue and provide a more detailed description?

[#3]

Hi

I got this error while add new host on the cluster. We had to restart the process few times because of misconfigured hostname and TLS setting on CM server.

Now after Host Instllation process finishes, CM directs me to Parcel distribution process.

However, CM runs parcel distribution process forever. When I check cloudera-scm-server.log, it was spitting out following msg indefinitely

2015-09-21 16:05:34,254 WARN 734582441@scm-web-60:com.cloudera.parcel.ClusterParcelStatus: Parcel not distributed but have active state ACTIVATING

I think CM updated status of the new host to ACTIVATING at somepoint previously failed installation attempt. Now it's confused.

How can we revert the host status and continue with parcel distribution process?

Thanks 

Ben

[#4]

It looks like you have arrived in an inconsistent state of wanting the parcel to be activated, but it is not distributed, most likely because the distributed parcels were deleted outside of Cloudera Manager.

To fix this, I presume that UI is stuck in "Activating" state, but there should be a "Cancel" button, that should reset your state so that you can distribute again. If there is no way to cancel, for whatever reason, you can force deactivate the parcel via API. http://cloudera.github.io/cm_api/apidocs/v6/path__clusters_-clusterName-_parcels_products_-product-_...

[#5]

Hi there:

Thanks for the reply. I followed your instruction, but still failed.

I tried this:

http://master:7180/api/v10/clusters/myCluster/parcels/products/SPARK/versions/0.9.0-1.cdh4.6.0.p0.98

It worked fine and returned a JSON object.

However, the following failed with 405 Method Not Allowed HTTP response code: 

http://master:7180/api/v10/clusters/myCluster/parcels/products/SPARK/versions/0.9.0-1.cdh4.6.0.p0.98/commands/deactivate

Any idea how I can fix that? Appreciate your help.

Andy

[#6]

Hi Andy,

The problem is that your browser is going to attempt an HTTP GET when the "deactivate" command requires a POST.  I recommend using curl or some other tool to issue the command as a post.

for example... 

curl -X POST ...

Ben 

[#7]

Hi Ben:

Awesome. Fixed with your suggested command. Appreciate it.

curl -u username:password -X POST http://master:7180/api/v10/clusters/myCluster/parcels/products/SPARK/versions/0.9.0-1.cdh4.6.0.p0.98/commands/deactivate

[#8]

Sometimes, This occurs if the agent cannot write data under /opt/cloudera/parcels/.flood, if your parcel is using by the other hosts, don't deactivate parcel as first step. Check directory space and delete /opt/cloudera/parcels/.flood folder and restart the agent.