I am guessing that the index has got corrupted somehow and deleted the data
directory on the slave. It has started copying the index. I'll report here
once that gets completed. If there is any other suggestion you might have
please reply back in the meantime. Thanks.
On Wed, Apr 19, 2017 at 12:21
Hello Shawn,
Thanks for taking the time out to help me. I had assigned 45GB to the heap
as starting memory and maximum memory it can use. The logs show the
following two warnings repeatedly :
- IndexFetcher : Cannot complete replication attempt because file
already exists.
-
On 4/14/2017 2:10 AM, Himanshu Sachdeva wrote:
> We're starting to upgrade our solr cluster to version 5.5. So we
> removed one slave node from the cluster and installed solr 5.5.4 on it
> and started solr. So it started copying the index from the master.
> However, we noticed a drop in the
Hi,
We're starting to upgrade our solr cluster to version 5.5. So we removed
one slave node from the cluster and installed solr 5.5.4 on it and started
solr. So it started copying the index from the master. However, we noticed
a drop in the replication speed compared to the other nodes which were
