I have just created https://issues.apache.org/jira/browse/SOLR-6205
I hope the description makes sens.
Thanks.
Arcadius.
On 23 June 2014 18:49, Mark Miller wrote:
> We have been waiting for that issue to be finished before thinking too
> hard about how it can improve things. There have been
We have been waiting for that issue to be finished before thinking too hard
about how it can improve things. There have been a couple ideas (I’ve mostly
wanted it for improving the internal zk mode situation), but no JIRAs yet that
I know of.
--
Mark Miller
about.me/markrmiller
On June 23, 201
https://issues.apache.org/jira/browse/ZOOKEEPER-107 maybe be implemented,
but it isn't in a release as yet :)
Its slated for 3.5.0 but given 3.4.0 came out in November 2011, and there
has been no minor release since then. The 3.4.x release is only releasing
critical fixes now, so any new function
On 3 February 2014 22:16, Daniel Collins wrote:
>
> One other option is in ZK trunk (but not yet in a release) is the ability
> to dynamically reconfigure ZK ensembles (
> https://issues.apache.org/jira/browse/ZOOKEEPER-107). That would give the
> ability to create new ZK instances in the event
sage-
From: Darrell Burgan
Sent: Wednesday, February 05, 2014 6:48 PM
To: solr-user@lucene.apache.org
Subject: RE: SolrCloud multiple data center support
Let's say I was primarily interested in ensuring there is a DR copy of the
search index that is replicated to the remote data
eisey [mailto:s...@elyograg.org]
Sent: Wednesday, February 05, 2014 12:39 AM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud multiple data center support
On 2/4/2014 10:14 PM, Darrell Burgan wrote:
> Interesting about the Zookeeper quorum problem. What if we were to run three
> Zookee
On 2/4/2014 10:14 PM, Darrell Burgan wrote:
> Interesting about the Zookeeper quorum problem. What if we were to run three
> Zookeepers in our primary data center and four in the backup data center. If
> we failed over, we wouldn't have a quorum, but we could kill one of the
> Zookeepers to rest
, February 03, 2014 11:44 AM
To: solr-user
Subject: Re: SolrCloud multiple data center support
SolrCloud has not tackled multi data center yet.
I don't think a or b are very good options yet.
Honestly, I think the best current bet is to use something like Apache Flume to
send data to both
ins [mailto:danwcoll...@gmail.com]
Sent: Monday, February 03, 2014 4:16 PM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud multiple data center support
Option a) doesn't really work out of the box, *if you need NRT support*.
The main reason (for us at least) is the ZK ensemble and maintaini
Option a) doesn't really work out of the box, *if you need NRT support*.
The main reason (for us at least) is the ZK ensemble and maintaining
quorum. If you have a single ensemble, say 3 ZKs in 1 DC and 2 in another,
then if you lose DC 2, you lose 2 ZKs and the rest are fine. But if you
lose the
SolrCloud has not tackled multi data center yet.
I don’t think a or b are very good options yet.
Honestly, I think the best current bet is to use something like Apache Flume to
send data to both data centers - it will handle retries and keeping things in
sync and splitting the stream. Doesn’t s
11 matches
Mail list logo
