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

There is a known issue where the Service Monitor in Cloudera Manager opens connections to ZooKeeper but due to a bug, doesn't close the connection. Your options are: 1. Disable HBase RegionServer Health Canary by changing the "HBase Region Health Canary" enabled flag in the HBase service configuration to false. This is the easiest solution. 2. Upgrade to a version of CM that includes the fix (4.8.5, 5.0.5, 5.1.4, 5.2.1, 5.3.0) 3. Frequently restart the service monitor (disruptive and not recommended) BTW please try to move away from Beta versions. Our latest relase is v5.3.0 and it is highly recommended that you migrate to it ... View more

> 1- to add a disk in a data node do i have to add disk in all node together . Each node can have a different number of disks. It's not ideal but not wrong to be so. > 2-do i have to update dfs.name.dir and dfs.data.dir both parameter ? If you're using this new disk for storing hdfs blocks, then update dfs.data.dir. If you're using it for namenode metadata, then update dfs.name.dir. > 3- do i have to update dfs.name.dir/dfs.data.dir on each data node in case i add disk on one data node . dfs.data.dir would be different on each datanode if they all have varying mount points and/or number of disks. ... 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