bq. In all my solr servers I have 40% free space
Well, clearly that's not enough if you're getting this error: "No
space left on device"
Solr/Lucene need _at least_ as much free space as the indexes occupy.
In some circumstances it can require more. It sounds like you're
having an issue with full
Thanks Daniel.
So, if I understand correctly the below exception is almost always
caused because of merging segments ? Though I see different file names
(for e.g download_av3.fdt in this case) in the exception messages
[explicit-fetchindex-cmd] ERROR
org.apache.solr.handler.ReplicationHand
On 1/3/2014 10:34 AM, Daniel Collins wrote:
We see this a lot as well, my understanding is that recovery asks the
leader for a list of the files that it should download, then it downloads
them. But if the leader has been merging segments whilst this is going on
(recovery is taking a reasonable p
We see this a lot as well, my understanding is that recovery asks the
leader for a list of the files that it should download, then it downloads
them. But if the leader has been merging segments whilst this is going on
(recovery is taking a reasonable period of time and you have an NRT system
where
Hey Annette,
Are you using Solr 4.0 final? A version of 4x or 5x?
Do you have the logs for when the replica tried to catch up to the leader?
Stopping and starting the node is actually a fine thing to do. Perhaps you can
try it again and capture the logs.
If a node is not listed as live but is
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
