Thanks to Erick. Get it.
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Tuesday, September 13, 2016 11:52 PM
To: dev@lucene.apache.org
Subject: Re: Index partition corrupted during a regular flush due to
FileNotFoundException on DEL file
bq: So can we
bq: So can we say that the FileNotFoundExcep tion on DEL file was
caused by merge operation of Lucene
Not quite. what we're saying is that unpredictable things _may_ happen
if your disk is full. You should check that you have adequate free
space for all operations to succeed. Lucene tries very
Thanks to Shawn.
So can we say that the FileNotFoundExcep tion on DEL file was caused by merge
operation of Lucene? Note that our application is running on old Lucene Core
v3.6.2. Does the rule below from Core 5.3.2 apply to Core 3.6.2?
Now we have 2 indexes in 68G and 76G respectively,
On 9/12/2016 7:07 PM, 郑文兴 wrote:
> So you mean if there is no more than 10G free space, Lucene/Solr will
> delete some files to save the disk space? Or it will cause the
> misbehave of Lucene/Solr?
If you do not have enough free disk space, and a segment merge takes
place that requires more free
BTW: From the log files, I can’t see other abnormal logs related with the
exception. But found the 1st exception:
[2016-09-12 16:08:47,628][ERROR][qtp2107666786-40502][indexEngine
] index [so_blog] commit ERROR:java.io.FileNotFoundException: _p5tr_328.del
Thanks to Erick. I will check the disk space first.
So you mean if there is no more than 10G free space, Lucene/Solr will delete
some files to save the disk space? Or it will cause the misbehave of
Lucene/Solr?
Please note that we have several shards/partitions under the same root
The del file should be present for each segment assuming it
has any documents that have been updated or deleted.
Of course if some process external to Solr removed it, you'd
get this error.
A less common reason is that your disk is full. Solr/Lucene
require that you have at least as much free
