In one of our CDH cluster (v5.0.0-beta1), zookeeper max connections are set to 60.
Now I found zookeeper logs out too many connections from Cloudera Manager.
view the connections by four-letter command 'cons', output show as follows:
view Cloudera Manager log, error information below occurs many times.
2015-01-12 11:50:32,445 ERROR [Parcel Update Service:components.ParcelDownloaderImpl@371] (3 skipped) Failed to download manifest. Status code: 404 URI: http://archive.cloudera.com/cdh5/parcels/latest/manifest.json
I wonder what conditions would cause Cloudera Manager to create massive connections to zookeeper.
and how do I solve it?
thanks in advance.
I am having the same issues with CM 5.7.5.
And most of the connections coming from the cloudera manager nodes.
@lwmonster If you read the previous comment from @GautamG the issue was resolved in a previous release. Unless something has changed this should be a seperate issue. I would suggest starting a new thread with further background on your specific situtaion.
hi, I have read the comment of @GautamG, I have tried the first suggestion, it do will not report Canary error on CM dashboard, but it still take all the connections of the machine which SERVICE MONITOR lies on. My CM version is 5.12.0, almost the latest, but seems the bug still exists.
I would suggest starting a new thread with all the details involved in your specific case.