d replication now? Our
>indexing is so slow that we cannot rely on a complete re-index of data
>from
>our DB of record (SQL) to recover data in the Solr indices.
>
>
>
>--
>View this message in context:
>http://lucene.472066.n3.nabble.com/Replicating-Between-Solr-Clouds-tp41
-Between-Solr-Clouds-tp4121196p4153856.html
Sent from the Solr - User mailing list archive at Nabble.com.
ple collections when using
zookeeper? How do you upload multiple sets of config files for each one and
keep them separate?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replicating-Between-Solr-Clouds-tp4121196p4121737.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 3/6/2014 7:54 AM, perdurabo wrote:
> Toby Lazar wrote
>> Unless Solr is your system of record, aren't you already replicating your
>> source data across the WAN? If so, could you load Solr in colo B from
>> your colo B data source? You may be duplicating some indexing work, but
>> at least you
g this
under a SolrCloud scenario.
Any other insight?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replicating-Between-Solr-Clouds-tp4121196p4121685.html
Sent from the Solr - User mailing list archive at Nabble.com.
data.
Toby
Sent via BlackBerry by AT&T
-Original Message-
From: Tim Potter
Date: Wed, 5 Mar 2014 02:51:21
To: solr-user@lucene.apache.org
Reply-To: solr-user@lucene.apache.org
Subject: RE: Replicating Between Solr Clouds
Unfortunately, there is no out-of-the-box solution for th
04, 2014 1:04 PM
To: solr-user@lucene.apache.org
Subject: Replicating Between Solr Clouds
We are looking to setup a highly available failover site across a WAN for our
SolrCloud instance. The main production instance is at colo center A and
consists of a 3-node ZooKeeper ensemble managing configs for a
sage in context:
http://lucene.472066.n3.nabble.com/Replicating-Between-Solr-Clouds-tp4121196.html
Sent from the Solr - User mailing list archive at Nabble.com.
