Mammoth 4.5 to 4.8 Upgrade Fails Due to the Cloudera Manager parameter "Maximum Non-Java Memory of Service Monitor" Getting Reset to 0 From the Existing Value

(Doc ID 2303033.1)

Last updated on SEPTEMBER 27, 2017

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 and later
Linux x86-64

Symptoms


During Mammoth Upgrade for example a 4.5 to 4.8 upgrade, upgrade fails because, "Maximum Non-Java Memory of Service Monitor" gets reset to 0 from the existing value. The existing value can be the default or a custom setting.

The sequence leading to this is:

1. Upgrade fails and Cloudera Manager shows the Cloudera Management Service (mgmt) is in bad health.  See:

2. Drilling down shows that the problem is due to "Maximum Non-Java Memory of Host Monitor". The error looks like:

mgmt: Maximum Non-Java Memory of Host Monitor
Could not parse: Maximum Non-Java Memory of Host Monitor: Could not parse parameter 'firehose_non_java_memory_bytes'. Was expecting a long
numeric value. Input.

See:

3. Navigating

Navigating in CM: mgmt > Instances > Service Monitor > Configuration > Search: Maximum Non-Java Memory of Service Monitor, shows that instead of the default value or custom value, the value is incorrectly set to "0" GB.

See:

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms