opt/vmware/horizon/workspace/logs shows entries similar to the following sample log entry {"errors":[{"code":"error.queryFailed","message":"Unable to execute query","parameters":{"reason":"{\"root_cause\":[{\"type\":\"circuit_breaking_exception\",\"reason\":\"[parent] Data too large, data for [<http_request>] would be [1018309538/971.1mb], which is larger than the limit of [986061209/940.3mb], real usage: [1018308392/971.1mb], new bytes reserved: [1146/1.1kb], usages [request=0/0b, fielddata=18070/17.6kb, in_flight_requests=1146/1.1kb, accounting=2117792/2mb]\",\"bytes_wanted\":1018309538,\"bytes_limit\":986061209,\"durability\":\"PERMANENT\"}],\"type\":\"circuit_breaking_exception\",\"reason\":\"[parent] Data too large, data for [<http_request>] would be [1018309538/971.1mb], which is larger than the limit of [986061209/940.3mb], real usage: [1018308392/971.1mb], new bytes reserved: [1146/1.1kb], usages [request=0/0b, fielddata=18070/17.6kb, in_flight_requests=1146/1.1kb, accounting=2117792/2mb]\",\"bytes_wanted\":1018309538,\"bytes_limit\":986061209,\"durability\":\"PERMANENT\"}"}}]}
VMware Identity Manager 3.3.7
The Opensearch service lacks sufficient HTTP content length capacity, and possibly Java memory heap allocation to process the size of the incoming HTTP requests.
To resolve the issue perform the following steps below
1. Take a backup/snapshot of the vIDM appliance(s)
2. Edit the configuration file /opt/vmware/opensearch/config/opensearch.yml on each vIDM appliance
3. Add the following parameter to the end of the file
http.max_content_length: 1000mb
4. Restart opensearch service on all appliances for the new settings to take effect
service opensearch restart
5. Continue to monitor the output in the analytics-service.log with the following command:
tail -f /opt/vmware/horizon/workspace/logs/analytics-service.log | grep -E " ERROR | WARN "If the issue persists, open a Broadcom Support case and reference this KB.