Thank you for your reply otis. I found two open issues which may relate to
this issue:
https://issues.apache.org/jira/browse/SOLR-4924
https://issues.apache.org/jira/browse/SOLR-4260
We recently changed some settings to make commits happen on a more periodic
nature (5 mins or 25000 docs). Before
Yes, sounds like it's because of the second node being in a different
AZ. In AWS, AZ really means a DC (Data Center), so the node that is
in a different AZ/DC is naturally going to replicate more slowly.
Otis
--
Solr & ElasticSearch Support -- http://sematext.com/
On Fri, Jun 14, 2013 at 8:5
Hi,
I currently have solrcloud setup with single shards and two nodes behind a
load balancer in aws. I also have an additional node in the cluster which
is outside the load balancer (not receiving any client requests) importing
data into the cluster using data import handler. So that takes my clus
