Data_streams matching ” + request.name + ” not found – How to solve this Elasticsearch error

Average Read Time

2 Mins

Data_streams matching ” + request.name + ” not found – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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 +

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content