How To Solve Issues Related to Log – Dangling index. exists on local file system. but not in cluster metadata. scheduling to delete in . auto import to cluster state

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Prevent Issue

Updated: Feb-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Dangling index. exists on local file system. but not in cluster metadata. scheduling to delete in . auto import to cluster state” it’s important to understand common problems related to Elasticsearch concepts: cluster, dangling, delete, discovery-file. See detailed explanations below complete with common problems, examples and useful tips.

DELETE Elasticsearch API

What is it

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.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Dangling Index Exists On Local File  

2Possible Bug In Elastic Causes Data  


Log Context

Log ”[{}] dangling index; exists on local file system; but not in cluster metadata; scheduling to delete in [{}]; auto import to cluster state [{}]” classname is LocalGatewayMetaState.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

                                     danglingIndices.put(indexName; new DanglingIndex(indexName; null));
                                } else if (danglingTimeout.millis() == 0) {
                                    logger.info("[{}] dangling index; exists on local file system; but not in cluster metadata; timeout set to 0; deleting now"; indexName);
                                    indicesService.deleteIndexStore("dangling index with timeout set to 0"; indexMetaData; state);
                                } else {
                                    logger.info("[{}] dangling index; exists on local file system; but not in cluster metadata; scheduling to delete in [{}]; auto import to cluster state [{}]"; indexName; danglingTimeout; autoImportDangled);
                                    danglingIndices.put(indexName;
                                            new DanglingIndex(indexName;
                                                    threadPool.schedule(danglingTimeout;
                                                            ThreadPool.Names.SAME;
                                                            new RemoveDanglingIndex(indexMetaData))));






About Opster

Opster identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to prevent issues, optimize performance and save resources.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster