The most likely cause is that the HBase Canary (part of HBase, not from Service Monitor) is pinging each region's health regularly. Prior to CM5.3.2, turning this HBase Canary off didn't work. So you could either - upgrade to CM 5.3.2 (or later). This should not lead to cluster downtime as only CM and agents will be upgraded. - lower the frequency of the the HBase Canary so that the discrepancy in stats is reduced. ... View more

In both lines, -Xmx52428800 is present, meaning maximum heap is 50MB. Please raise it to a more reasonable size like 512MB or more and try again ... View more

I set up a CM5.4.1 + CDH5.4.1 single node cluster and tried to upgrade (cluster -> upgrade). I see this text with CDH5.4.2 parcel selected for upgrade.​ This wizard will upgrade CDH running on this cluster from CDH 5.4.1 to the version selected below. This wizard supports the following scenarios: - Major version upgrades from CDH 4 to CDH 5. - Minor version upgrades from CDH 5.x to CDH 5.y. - Maintenance releases from CDH a.b.x to CDH a.b.y Please show us a screenshot​ where you see CDH5.4.2 not being offered for upgrade. ... View more

Please verify that /tmp on both hosts do not have the noexec option set. You can verify this by running /bin/mount and checking the mount options. If you are able to, remount /tmp without noexec and try starting the NodeManager again ... View more