Error: CircuitBreakingException [parent] Data too large in VMware Identity Manager 3.3.7 OpenSearch

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

VMware Identity Manager (vIDM) 3.3.7 appliances may experience intermittent service failures where the OpenSearch service enters a "not running" state. This article provides the steps to resolve CircuitBreakingException errors associated with memory exhaustion.

 

• OpenSearch service intermittently stops and requires manual restart (/etc/init.d/opensearch restart).
• horizon.log or OpenSearch logs show the following error: org.opensearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [internal:cluster/shard/failure] would be ...

Environment

VMware Identity Manager (vIDM) 3.3.7 OpenSearch

Cause

The OpenSearch JVM heap exceeds the configured memory limit during search or aggregation operations, triggering the circuit breaker to prevent an OutOfMemoryError.

Resolution

To resolve this issue, adjust the OpenSearch JVM heap size:

1. Access the vIDM appliance via SSH.
2. Navigate to the jvm.options file (location varies by environment; typically /opt/vmware/opensearch/config/jvm.options).
3. Modify the heap size parameters to increase memory allocation, for example: -Xms2g -Xmx2g
4. Restart the OpenSearch service: /etc/init.d/opensearch restart
5. Monitor the cluster health using the following command: curl 'http://localhost:9200/_cluster/health?pretty=true'

If the issue persists, ensure the root partition is not full and review the gc.log files for excessive growth.

Additional Information

• To retrieve and review logs, refer to Retrieving vIDM Appliance Logs.
• For further assistance, please contact Broadcom Support: Contact Broadcom Support.
• To subscribe to updates regarding this issue, reference: How to subscribe to Knowledge Base articles.