IBM Support

QRadar SOAR: Elasticsearch index corruption caused by an OutOfMemoryError

Troubleshooting


Problem

An OutOfMemoryError in Elasticsearch can corrupt the indices that IBM Security QRadar SOAR uses to search. This document describes how to identify and resolve this kind of problem.

Symptom

If search is returning error messages to the UI, you are seeing error messages in the logs or IBM Security QRadar SOAR needs to be restarted then it is worth checking if there is a corruption of the indices.

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:
19 June 2024

UID

ibm16211016