>
> So then the Q becomes: if we have 10 ZK nodes and they split in 5 & 5
> nodes, does that mean neither side will have quorum because having 10 ZKs
> was a bad number of ZKs to have to begin with?
Right - from the ZooKeeper admin guide, under Clustered Setup:
"Because Zookeeper requires a majo
om/spm
- Original Message -
> From: Mark Miller
> To: solr-user
> Cc:
> Sent: Monday, June 18, 2012 11:05 AM
> Subject: Re: SolrCloud and split-brain
>
>
> On Jun 15, 2012, at 10:33 PM, Otis Gospodnetic wrote:
>
>> However, if my half brain understan
On Jun 15, 2012, at 10:33 PM, Otis Gospodnetic wrote:
> However, if my half brain understands what split brain is then I think that's
> not a completely true claim because one can get unlucky and get a SolrCloud
> cluster partitioned in a way that one or even all partitions reject indexing
> (
On Sat, Jun 16, 2012 at 5:33 AM, Otis Gospodnetic
wrote:
> And here is one more Q.
> * Imagine a client is adding documents and, for simplicity, imagine SolrCloud
> routes all these documents to the same shard, call it S.
> * Imagine that both the 7-node and the 3-node partition end up with a
>
June 15, 2012 5:07 PM
> Subject: Re: SolrCloud and split-brain
>
>
> On Jun 15, 2012, at 3:21 PM, Otis Gospodnetic wrote:
>
>> Thanks Mark, will open an issue in a bit.
>>
>> But I think the following is the real meat of the Q about split brain and
> SolrClo
fine
- it will become the leader.
>
>
>
> Otis
>
> Performance Monitoring for Solr / ElasticSearch / HBase -
> http://sematext.com/spm
>
>
>
> - Original Message -
>> From: Mark Miller
>> To: solr-user
>> Cc:
>> Sent
exing request will be rejected. Is this correct?
Otis
Performance Monitoring for Solr / ElasticSearch / HBase -
http://sematext.com/spm
- Original Message -
> From: Mark Miller
> To: solr-user
> Cc:
> Sent: Friday, June 15, 2012 2:22 PM
> Subject: Re: SolrCl
On Jun 15, 2012, at 2:12 PM, Otis Gospodnetic wrote:
> Makes sense. Do responses carry something to alert the client that
> "something is rotten in the state of cluster"?
No, I don't think so - we should probably add that to the header similar to how
I assume partial results will work.
Feel
Ola,
Thanks Mark!
>> Does this work even when outside clients (apps for indexing or searching)
> send their requests directly to individual nodes?
>> Let's use the example from my email where we end up with 2 groups of
> nodes: 7-node group with 2 ZK nodes on the same network and 3-node gro
On Jun 15, 2012, at 1:44 PM, Otis Gospodnetic wrote:
> Does this work even when outside clients (apps for indexing or searching)
> send their requests directly to individual nodes?
> Let's use the example from my email where we end up with 2 groups of nodes:
> 7-node group with 2 ZK nodes on th
Hi,
> Zookeeper avoids split brain using Paxos (or something very like it - I
> can't remember if they extended it or modified and/or what they call it).
>
> So you will only ever see one Zookeeper cluster - the smaller partition will
> be
> down. There is a proof for Paxos if I remember rig
Zookeeper avoids split brain using Paxos (or something very like it - I can't
remember if they extended it or modified and/or what they call it).
So you will only ever see one Zookeeper cluster - the smaller partition will be
down. There is a proof for Paxos if I remember right.
Zookeeper then
On 6/15/2012 12:49 PM, Otis Gospodnetic wrote:
> Hi,
>
> How exactly does SolrCloud handle split brain situations?
>
> Imagine a cluster of 10 nodes.
> Imagine 3 of them being connected to the network by some switch and imagine
> the out port of this switch dies.
> When that happens, these 3 nod
13 matches
Mail list logo