CM uses BitTorrent to distrubte parcels so it's already very efficient.   My recommendation would be to let CM do the work and not bother with trying to save yourself a few minutes. ... View more

Good news. If that resolves your issue, please spare some time in accepting the solution. Thanks. ... View more

Your Welcome! ... View more

That worked, thanks! Now I can see the option on the ambari UI. ... View more

I have the same issue using 5.5 quickstart VM. Unfortunately downloading and activating the parcels do not resolve the issue.   Every time when VM is started, the status becomes unknow, and it is fine after manually restart the Cloudera Management Service. The error is 'com.cloudera.cmf.BasicScmProxy connection refused'. It is such a bad experience of starting using Cloudera. ... View more

I manage to create python script to change the configuration. here is an example: https://linuxlabrat.wordpress.com/2015/05/26/updating-cdh-configuration-using-python-and-rest-apis/ ... View more

Thanks we'll do that. i.e. - currently we'll add the flag under init.d for the long run we'll create an alternative robust DB.   Doron ... View more

Not an issue Mshirley, many thanks for your comments.   To be honest, I didn't check the cloudera-scm-agent logs after the restart so cannot say whether there were any errors reported. I'll keep that in mind next time onwards.   Also, /opt/cloudera/parcels directory contained 2 files - one was named CDH (a link to the CDH5.3 directory, I suppose) and the actual CDH5.3xxxx directory (sorry, cannot recollect the exact name) which contained the /lib /bin and several other parcel directories . And yes, we did try deactivating the old parcel before downloading the new one. Unfortunately, nothing worked.   Around the same time, we also did a reboot and noticed that one of the nodes did not come up. As a result, we were forced to do the re-installation again.  ... View more