bq: Why not use classic replication between one node in the cluster and another
node in the other cluster.
First of all in SolrCloud I'm pretty sure you can't do that, where
"that" is have
classic replication operate where the source was one SolrCloud and
the destination is another SolrCloud clust
Erick,
That's not what I was going for. No code porting. I was thinking this:
Why not use classic replication between one node in the cluster and another
node in the other cluster?
something along this line.
Thanks,
--Abdel.
On Tue, May 10, 2016 at 12:21 AM, Erick Erickson
wrote:
> bq: How sim
bq: How similar thing could be done in 4.9.1?
That's not going to happen. More precisely,
there is zero chance that anyone will take on that
work unless it's a custom one-off that you
hire done or develop internally. And even
if someone took this on, it'd never be officially
released.
IOW, if you
Hi Alex,
just started reading about CDCR, looks very promissing. Is this only in
6.0? our PROD server are running 4.9.1 and we cannot upgrade just yet. How
similar thing could be done in 4.9.1?
Thanks,
--Abdel
On Mon, May 9, 2016 at 2:59 PM, Alexandre Rafalovitch
wrote:
> Have you looked at Cr
Have you looked at Cross Data Center replication that's the new big
feature in Solr 6.0?
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 10 May 2016 at 02:13, Abdel Belkasri wrote:
> Hi there,
>
> we have the main site setup as
Hi there,
we have the main site setup as follows:
solrCould:
App --> smart Client (solrj) --> ensemble of zookeeper --> SolrCloud Noes
(with slice/shard/recplica)
Works fine.
On the DR site we have a mirror setup, how can we keep the two site in
sync, so that if something happened we point th
