Hi,
I found out the problem by myself.
The reason was a bad deployment of of Solr on tomcat. Two instances of
solr were instantiated instead of one. The two instances were managing
the same indexes, and therefore were trying to write at the same time.
My apologies for the noise created on the ml,
--
Renaud Delbru
On 30/05/11 21:52, Renaud Delbru wrote:
Hi,
For months, we were using apache solr 3.1.0 snapshots without problems.
Recently, we have upgraded our index to apache solr 3.1.0,
and also moved to a multi-core infrastructure (4 core per nodes, each
core having its own index).
We found that one of the index slave started to show failure, i.e.,
query errors. By looking at the log, we observed some errors during the
latest snappull, due to two type of exceptions:
- java.io.FileNotFoundException: File does not exist ...
and
- java.nio.channels.OverlappingFileLockException: null
Then, after the failed pull, the index started to show some index
related failure:
java.io.IOException: read past EOF at
org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:207)]
However, after manually restarting the node, everything went back to
normal.
You can find a more detailed log at [1].
We are afraid to see this problem occurring again. Have you some idea on
what can be the cause ? Or a solution to avoid such problem ?
[1] http://pastebin.com/vbnyrUgJ
Thanks in advance
