On 2/10/2016 8:02 AM, tedsolr wrote:
> I have my head wrapped around sending index requests in parallel, but in a
> later post you mentioned how you separately track the most recent update and
> are able to sync from that point if needed. That I don't get. Is it an index
> version you are tracking?
View this message in context:
http://lucene.472066.n3.nabble.com/replicate-indexing-to-second-site-tp4256240p4256404.html
Sent from the Solr - User mailing list archive at Nabble.com.
://lucene.472066.n3.nabble.com/replicate-indexing-to-second-site-tp4256240p4256399.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hello Ted.
We have a similar requirement to deploy Solr across 2 DCs.
In our case, the DCs are connected via fibre optic.
We managed to deploy a single SolrCloud cluster across multiple DCs without
any major issue (see links below).
The whole set-up is described in the following articles:
-
htt
I agree. If the system updates synchronously, then you are in two-phase commit
land. If you have a persistent store that each index can track, then things are
good.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Feb 9, 2016, at 7:37 PM, Shawn Heis
On 2/9/2016 5:48 PM, Walter Underwood wrote:
> Updating two systems in parallel gets into two-phase commit, instantly. So
> you need a persistent pool of updates that both clusters pull from.
My indexing system does exactly what I have suggested for tedsolr -- it
updates multiple copies of my ind
the users. Is
> this just a software problem to work out (separate thread)? Or is there a
> SolrJ solution (asyc calls)?
>
> Thanks!!
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/replicate-indexing-to-second-site-tp4256240.html
> Sent from the Solr - User mailing list archive at Nabble.com.
Updating two systems in parallel gets into two-phase commit, instantly. So you
need a persistent pool of updates that both clusters pull from.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Feb 9, 2016, at 4:15 PM, Shawn Heisey wrote:
>
> On 2/9/2
On 2/9/2016 1:43 PM, tedsolr wrote:
> I expect that rsync can be used initially to copy the collection data
> folders and the zookeeper data and transaction log folders. So after
> verifying Solr/ZK is functional after the install, shut it down and perform
> the copy. This may sound slow but my pro
ut I don't want to lengthen the response time for the users.
>> Is
>> this just a software problem to work out (separate thread)? Or is there a
>> SolrJ solution (asyc calls)?
>>
>> Thanks!!
>>
>>
>>
>> --
>> View this message in context:
>> http://lucene.472066.n3.nabble.com/replicate-indexing-to-second-site-tp4256240.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
? Seems
> reasonable but I don't want to lengthen the response time for the users.
> Is
> this just a software problem to work out (separate thread)? Or is there a
> SolrJ solution (asyc calls)?
>
> Thanks!!
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/replicate-indexing-to-second-site-tp4256240.html
> Sent from the Solr - User mailing list archive at Nabble.com.
abble.com/replicate-indexing-to-second-site-tp4256240.html
Sent from the Solr - User mailing list archive at Nabble.com.
12 matches
Mail list logo