> Sent: Monday, March 30, 2015 6:40 PM
> To: solr-user@lucene.apache.org
> Subject: Re: how do you replicate solr-cloud between datacenters?
>
> That's an open issue. See:
> https://issues.apache.org/jira/browse/SOLR-6273
>
> -- Jack Krupansky
>
> On Mon, Mar 30, 2
I got the answer to my most recent question without even asking it!
Thanks
-Original Message-
From: Jack Krupansky [mailto:jack.krupan...@gmail.com]
Sent: Monday, March 30, 2015 6:40 PM
To: solr-user@lucene.apache.org
Subject: Re: how do you replicate solr-cloud between datacenters
That's an open issue. See:
https://issues.apache.org/jira/browse/SOLR-6273
-- Jack Krupansky
On Mon, Mar 30, 2015 at 5:45 PM, Timothy Ehlers wrote:
> Can you use /replication ??? How would you do this between datacenters?
>
> --
> Tim Ehlers
>
Can you use /replication ??? How would you do this between datacenters?
--
Tim Ehlers
rch system will still be up if the other machine(s) are up and
running.
-
Thanks,
Michael
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replicate-Solr-Cloud-tp4100410p4100434.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi
i want to create solr cloud like this:
1 solr cloud in location A, and another solr cloud in location B how to
make that solr cloud is location B is replicate solr cloud in location A.
And if all node in slor cloud A is die slor cloud B is still working and
vice versa.
any body know how to
On the lengthy TODO list is making SolrCloud nodes "rack aware"
that should help with this, but it's not real high in the priority queue
as I recall. The current architecture sends updates and requests
all over the cluster, so there are lots of messages that go
across the presumably expensive pipe
Uh, I remember that email, but can't recall where we did it will
try to recall it some more and reply if I can manage to dig it out of
my brain...
Otis
--
Solr & ElasticSearch Support -- http://sematext.com/
Performance Monitoring -- http://sematext.com/spm
On Tue, Jun 25, 2013 at 2:24 PM,
Also, you have to track two sets of batches, failures, and retries. --wunder
On Jun 25, 2013, at 11:30 AM, Kevin Osborn wrote:
> Jason,
>
> My initial reluctance to indexing directly to both data centers is that we
> are doing a lot of bulk loading through CSV handler. We never get just 1
> do
Jason,
My initial reluctance to indexing directly to both data centers is that we
are doing a lot of bulk loading through CSV handler. We never get just 1
document at a time. It comes in large batch updates. And now we would have
to send the batch updates twice.
That is not to say that we won't g
Otis,
I did actually stumble upon this link.
http://comments.gmane.org/gmane.comp.jakarta.lucene.solr.user/74870
This was from you. You were attempting to replicate data from SolrCloud to
some other slaves for heavy-duty queries. You said that you accomplished
this. Can you provide a few pointer
Kevin,
I can imagine this working if you consider your second data center a pure slave
relationship to your SolrCloud cluster. I haven't tried it, but I don't see
why the solrconfig.xml can't identify as a master allowing you to call any of
your cores in the cluster to replicate out. That bei
I think what is needed is a Leader that, while being a Leader for its
own Slice in its local Cluster and Collection (I think I'm using all
the latest terminology correctly here), is at the same time a Replica
of its own Leader counterpart in the "Primary Cluster".
Not currently possible, AFAIK.
Or
We are going to have two datacenters, each with their own SolrCloud and
ZooKeeper quorums. The end result will be that they should be replicas of
each other.
One method that has been mentioned is that we should add documents to each
cluster separately. For various reasons, this may not be ideal fo
14 matches
Mail list logo
