How To Solve Issues Related to Log – Failed to write failed status for river creation

How To Solve Issues Related to Log – Failed to write failed status for river creation

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Failed to write failed status for river creation” it’s important to understand a few problems related to Elasticsearch concepts plugin. See bellow important tips and explanations on these concepts

Log Context

Log”failed to write failed status for river creation” classname is RiversService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
                client.prepareIndex(riverIndexName; riverName.name(); "_status")
                        .setConsistencyLevel(WriteConsistencyLevel.ONE)
                        .setSource(builder).execute().actionGet();
            } catch (Exception e1) {
                logger.warn("failed to write failed status for river creation"; e);
            }
        }
    }

    public synchronized void closeRiver(RiverName riverName) throws ElasticsearchException {




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

 

Unstable Cluster  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now