Standby NameNode Intermittently Goes into Bad Health with NAME_NODE_RPC_LATENCY Health Test Failures
(Doc ID 2435153.1)
Last updated on JULY 20, 2024
Applies to:
Big Data Appliance Integrated Software - Version 4.11.0 and laterLinux x86-64
Symptoms
The symptom here is that the Standby NameNode intermittently goes into bad health with NAME_NODE_RPC_LATENCY health test failures.
Drilling down into the Health Tests reports:
RPC Latency
The moving average of the RPC latency was 13.4 second(s) ms over the previous 5 minute(s).
The moving average of the queue time was 0 second(s) ms.
The moving average of the processing time was 13.4 second(s) ms. Critical threshold: 5 second(s).
The moving average of the RPC latency was 13.4 second(s) ms over the previous 5 minute(s).
The moving average of the queue time was 0 second(s) ms.
The moving average of the processing time was 13.4 second(s) ms. Critical threshold: 5 second(s).
The example here is from a BDA V4.11/CDH 5.13 cluster.
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 |