Briefly, this error occurs when Elasticsearch tries to delete a river (a data feed mechanism) during the stop process, but fails. This could be due to the river not existing, insufficient permissions, or a network issue. To resolve this, ensure the river exists before deletion, check the user has the correct permissions to delete rivers, and verify the network connection is stable. If the river is no longer needed, you can ignore this error. However, if it’s required, recreate it and ensure it’s functioning properly.
This guide will help you check for common problems that cause the log ” failed to delete river on stop [{}]/[{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete.
Overview
DELETE is an Elasticsearch API which removes a document from a specific index. This API requires an index name and _id document to delete the document.
Delete a document
DELETE /my_index/_doc/1
Notes
- A delete request throws 404 error code if the document does not already exist in the index.
- If you want to delete a set of documents that matches a query, you need to use delete by query API.
Log Context
Log “failed to delete river on stop [{}]/[{}]” classname is RiversService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
Override
public void run() {
try {
closeRiver(riverName);
} catch (Exception e) {
logger.warn("failed to delete river on stop [{}]/[{}]"; e; riverName.type(); riverName.name());
} finally {
latch.countDown();
}
}
});
