My Oracle Support Banner

Navigator Metadata Server Exits Unexpectedly (Doc ID 2205122.1)

Last updated on FEBRUARY 05, 2020

Applies to:

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

Symptoms

Navigator Metadata Server exits unexpectedly with the following:

The health test result for NAVIGATORMETASERVER_SCM_HEALTH has become bad:
This role's process is starting. This role is supposed to be started.
...
Unexpected Exits (mgmt, Navigator Metadata Server, <HOSTNAME3>)

and

Bad: This role encountered 1 unexpected exit(s) in the previous 5 minute(s).
This included 1 exit(s) due to OutOfMemory errors. Critical threshold any.

 

As background, the Navigator Metadata Server health test checks that the Navigator Metadata Server has not recently exited unexpectedly. The test returns "Bad" health if the number of unexpected exits exceeds a critical threshold.  For example, if the Navigator Metadata Server health test is configured with a critical threshold of 1, this test returns "Good" health if there have been no unexpected exits recently. If 1 or more unexpected exits have occurred recently, the test returns "Bad" health.

The Navigator Metadata Server health test also indicates if any of the exits were caused by an OutOfMemory error if the Cloudera Manager "Kill When Out of Memory" monitoring setting is enabled. 

You can configure the Navigator Metadata Server health test using "Unexpected Exits Thresholds" and "Unexpected Exits Monitoring Period" Navigator Metadata Server monitoring settings.

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.