As another data point, this happened on another index:
java.io.IOException: background merge hit exception: _17a:C1003710
_18h:C66391 _1ct:C45384 _1wt:C104479 _1zo:C23469 _271:C58570
_2dk:C53760 _2h5:C109879 _2ik:C7713 _2ii:C121 _2ij:C243 _2il:C124
_2im:C122 _2in:C115 _2io:C138 _2ip:C131 _2iq:C116
Correction - this was with Lucene 2.9.3.
On 26 July 2010 14:21, David Sitsky wrote:
> Hi,
>
> A customer has been indexing a very large collection of documents that
> has been running over many days using 2.9.0. During the optimisation
> stage, the following error occurred, and now the index can
Hi,
A customer has been indexing a very large collection of documents that
has been running over many days using 2.9.0. During the optimisation
stage, the following error occurred, and now the index can no longer
be opened due to the "missing file". I have been told this index is
on a local RAID
