I've never had to do that, but a quick Google search brought this up:
http://stackoverflow.com/questions/9935177/how-to-repair-corrupted-lucene-index
Another (possibly better and definitely safer) solution would be to log
your updates in a way that would allow you to reprocess them in sequence.
It
I'd write a shutdown method that calls close() in a controlled manner
and invoke it at 23:55. You could also call commit() at whatever
interval makes sense to you but if you carried on killing the JVM
you'd still be liable to lose any docs indexed since the last commit.
This is standard stuff jus
Team,
We have our app using lucene 4.1. Docs keep getting indexed and we
close the index by 00.00 hrs every day and open a new one for the next
calendar day, however in case of an abrupt shutdown/kill of the JVM, the
app server crashes and the live indexes end up remaining without a
segme
