You should not do this yourself. You can control the amount of space that CM consumes in these directories via the Time-Series Storage configuration of HMON and SMON. There's a 10 GB minimum for both, meaning you can expect 20 GB to be consumed by these two roles eventually. It is possible, though discouraged to set a lower limit, though you have to use the cmon.conf safety valve. You can enter a number of bytes to use as a maximum -- something like below where XXX is the number of bytes. This requires an SMON or HMON restart, but it should very quickly cleanup to the limit specified. Again, this is something we don't really test with outside of some dev clusters, so proceed with caution. firehose_time_series_storage_bytes XXX chris ... View more

Thnaks. That's helpful. I've got a few more questions:   #1. What version of Impala are you running? If you hit 'XXX/jsonmetrics' on the catalog server web UI what do you see? What about 'XXX/jsonmetrics?json'.   #2. Can you confirm that the CM agent process running is 5.4? That is: when you upgraded to 5.4 did you both upgrade the CM agent software and restart the CM agent software (service cloudera-scm-agent restart).   #3. Can you post the contents of the cloudera-monitor.properties for the catalog server? You can get this by going to the catalog server status page -> processes tab -> configuration files -> cloudera-monitor.properties. ... View more

Could you post the exact text or a screenshot of the alert you're seeing? If you could post or email me the CM agent.log (/var/log/cloudera-scm-agent.log) that might help narrow this down as well.   We did make a change in this area in CM 5.4, but it was to make monitoring of the TLS enabled Catalog Server web UI work properly.   ... View more