IBM Support

OutOfMemoryError Corrupts QRadar SOAR Search Indices in Elasticsearch/OpenSearch – Symptoms, Logs, and Recovery Steps

Troubleshooting


Problem

An OutOfMemoryError in Elasticsearch/OpenSearch can corrupt the search indices used by IBM Security QRadar SOAR. This document describes how to identify and resolve this type of problem.

Symptom

If search is returning errors in the UI, errors are appearing in the logs, or IBM Security QRadar SOAR requires frequent restarts, it is worth checking whether the search indices have become corrupted.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSA230","label":"IBM Security QRadar SOAR"},"ARM Category":[{"code":"a8m0z0000001grPAAQ","label":"Resilient Core-\u003ESearch"}],"ARM Case Number":"TS003720163","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
03 July 2026

UID

ibm16211016