This situation may happen when one or two nodes hit some problem downloading or activating the parcel. A common cause is wrong permission or ownership on one of the parcel directories on the nodes. One thing you can try to diagnose the problem is to abort the parcel activation using the Cloudera Manager REST API. To do this, use curl to invoke the API command, such as the following example:
curl -k -X POST -u admin:admin https://localhost:7183/api/v17/clusters/mycluster/parcels/products/SPARK2/versions/2.3.0.cloudera5-1.cdh5.13.3.p0.802571/commands/deactivate
Replace the highlighted portion appropriately. If you are unsure of the product name and version, use curl to retrieve the information:curl -k -u admin:admin https://localhost:7183/api/v17/clusters/mycluster/parcels
The command will return you a json result like below:{
"items" : [ {
"product" : "CDH",
"version" : "5.15.3-1.cdh5.15.3.p0.77",
"stage" : "ACTIVATED",
"clusterRef" : {
"clusterName" : "Cluster 1"
}
}, {
"product" : "SPARK2",
"version" : "2.3.0.cloudera5-1.cdh5.13.3.p0.802571",
"stage" : "ACTIVATING",
"clusterRef" : {
"clusterName" : "Cluster 1"
}
}, {
.....
} ]
}
No comments:
Post a Comment