TooManyOpenFiles might cause data-loss in ElasticSearch (Lucene) #2812

Closed
s1monw opened this Issue Mar 22, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@s1monw
Contributor

s1monw commented Mar 22, 2013

Under certain circumstances a TooManyOpenFiles exception (in Java thrown as FileNotFoundException) might cause data loss where entire shards (lucene indices) are deleted. This is mainly caused by Lucene-4870 - currently all Elasticsearch releases are affected by this.

@ghost ghost assigned s1monw Mar 22, 2013

@s1monw s1monw closed this in 560d2c0 Mar 22, 2013

s1monw added a commit that referenced this issue Mar 22, 2013

Fix issue where entire shards are lost due to too many open files exc…
…eptions and a but in Lucene's

IndexWriter / DirectoryReader where an existsing index was not detected and then deleted due to a wrong
creation mode. See LUCENE-4870

Closes #2812

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Fix issue where entire shards are lost due to too many open files exc…
…eptions and a but in Lucene's

IndexWriter / DirectoryReader where an existsing index was not detected and then deleted due to a wrong
creation mode. See LUCENE-4870

Closes #2812
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment