Description
The system checks the garbage collection (GC) duration of the MZooKeeper process every 60 seconds. This alarm is generated when the ****uration exceeds the threshold (12 seconds by default).
This alarm is cleared when the (GC) duration is less than the threshold.
Possible Causes
The heap memory of the MZooKeeper instance is overused or the heap memory is inappropriately allocated. As a result, GCs occur frequently.
Solution
Log in to FusionInsight Manager.
On the FusionInsight Manager portal, choose O&M > Alarm > Alarm. On the displayed interface, click the drop-down button of ALM-43903
****uration of the MZooKeeper Process Exceeds the Threshold. check the IP address of the instance for which the alarm is generated.
On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Service > MZooKeeper > Instance > Mquorumpeer(IP address for which the alarm is generated). Click the drop-down menu in the upper right corner of Chart, choose Customize > GC, and select MZooKeeper ****uration per Minute to check the ****uration statistics of the MZooKeeper process collected every minute.
Check whether the ****uration of the MZooKeeper process collected every minute exceeds the threshold (12 seconds by default).
If yes, go to 5.
If no, go to 8.
On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Service > MZooKeeper > Configuration > All Configurations > Mquorumpeer > System to increase the value of -Xmx configured in the GC_OPTS parameter as required.
Save the configuration and restart the MZooKeeper service.
Check whether the alarm is cleared.
If yes, no further action is required.
If no, go to 8.