Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.
Take a self-guided product tour to see for yourself (no registration required).This guide will help you check for common problems that cause the log ” data_streams matching ” + request.name + ” not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, indices and request.
Log Context
Log “data_streams matching [” + request.name + “] not found”classname is DeleteDataStreamAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// if a match-all pattern was specified and no data streams were found because none exist; do not
// fail with data stream missing exception
if (Regex.isMatchAllPattern(request.name)) {
return currentState;
}
throw new ResourceNotFoundException("data_streams matching [" + request.name + "] not found");
}
Set snapshottingDataStreams = SnapshotsService.snapshottingDataStreams(currentState; dataStreams);
if (snapshottingDataStreams.isEmpty() == false) {
throw new SnapshotInProgressException("Cannot delete data streams that are being snapshotted: " + snapshottingDataStreams +
Find & fix Elasticsearch problems
