Dear Gautam,   Thanks for response. It is because of disk space. I did not notice that my d drive have lack of space. I destoryed and installed in another drive which have sufficent disk space. It worked fine.   Regards Mani ... View more

The files within the parcel are not modified after installation. When you make configuration changes and restart the role, Cloudera Manager will send the updated files to the agent which will stash it under /var/run/cloudera-scm-agent/process. Any client configuration changes will appear in /etc//conf You can read about how Cloudera Manager manages roles and services in this blog post. http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/ ... View more

Cloudera doesn't have an official position on this tool yet. The project page does mention that Hadoop 2.0 is not supported, so I doubt it will work with CDH 5.2.1. You're of course welcome to provide feedback if you do try it. Note that Cloudera Manager does allow you to monitor several metrics across the cluster. Maybe if you had specific questions on tasks, we can assist without having to use an extra tool. ... View more

Unfortunately I cannot think of anything further. You could try talking to the network admins at your client site to see why it might be failing. Their proxy logs would have the answer ... View more

If your services (eg: HDFS, HBase) are marked as dependent on that ZooKeeper service, then the ensemble will a part of their config (hdfs-site.xml, hbase-site.xml). If your application uses HBase for example, then mark the node as a gateway which will deploy the config in /etc/hbase, then let your app use those. If you're running a custom app that has its own set of config files, then you should provide all ZooKeeper servers. Pointing to only one would mean you might face an outage if it is down. The ZooKeeper client libraries know how to deal with multiple servers and switch connections if one goes down. ... View more