How to remove write-lock for elasticsearch segment after reindexing?

How to remove write-lock for Elasticsearch segment after reindexing?

Looking at the stack trace there is a missing Lucene file which is not good. Did this index/shard have any docs in it before shutdown? Can you list the current files in the data1/data/nodes/0/indices/XqfshaweRp-5GAXbK7C_qA/23/index directory?

Caused by: java.io.FileNotFoundException: no segments* file found in store(mmapfs(E:\nice_systems\RTServer\Elasticsearch\data\nodes\0\indices\AgGE3T0CQqmNUbTa7mgxog\0\index)): files: [recovery.AXzg-JDdOOIh9tEF6n7G._f7t.dii, recovery.AXzg-JDdOOIh9tEF6n7G._f7t.fdx, recovery.AXzg-JDdOOIh9tEF6n7G._f7t_2.liv, recovery.AXzg-JDdOOIh9tEF6n7G._f8p.si, recovery.AXzg-JDdOOIh9tEF6n7G._f8q.cfe, write.lock]

Originally posted by @markharwood in #30919 (comment)

What's the question here @Adarsh_Nair ?

How to remove write-lock for Elasticsearch segment after reindexing?

Error we are getting is -
Caused by: java.io.FileNotFoundException: no segments* file found in store(mmapfs(E:\nice_systems\RTServer\Elasticsearch\data\nodes\0\indices\AgGE3T0CQqmNUbTa7mgxog\0\index)): files: [recovery.AXzg-JDdOOIh9tEF6n7G._f7t.dii, recovery.AXzg-JDdOOIh9tEF6n7G._f7t.fdx, recovery.AXzg-JDdOOIh9tEF6n7G._f7t_2.liv, recovery.AXzg-JDdOOIh9tEF6n7G._f8p.si, recovery.AXzg-JDdOOIh9tEF6n7G._f8q.cfe, write.lock]

How can this be resolved?

There is no need to manually remove anything from the data path. The error you shared is not a big problem and (as long as nothing else is wrong) Elasticsearch will resolve it itself.

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.