ale.
>
>
> Best regards,
>
> - Andy
>
>
>>____________
>> From: Mohit Anchlia
>>To: user@hbase.apache.org
>>Sent: Saturday, December 3, 2011 5:48 AM
>>Subject: Re: HBase and Consistency in CAP
>>
>>Thanks. I am having
ise. The Google paper includes some
discussion of this design rationale.
Best regards,
- Andy
>
> From: Mohit Anchlia
>To: user@hbase.apache.org
>Sent: Saturday, December 3, 2011 5:48 AM
>Subject: Re: HBase and Consistency in CAP
>
>T
Thanks. I am having just bit of conflict in understanding how is
random node failure different than network partition? In both cases
there is an impact clearly visible to the user (time it takes to
failover and replay logs)?
On Fri, Dec 2, 2011 at 1:42 PM, Ian Varley wrote:
> The simple answer is
The simple answer is that HBase isn't architected such that 2 region servers
can simultaneously host the same region. In addition to being much simpler from
an architecture point of view, that also allows for user-facing features that
would be difficult or impossible to achieve otherwise: single
Thanks for the overview. It's helpful. Can you also help me understand
why 2 region servers for the same row keys can't be running on the
nodes where blocks are being replicated? I am assuming all the
logs/HFiles etc are already being replicated so if one region server
fails other region server is
Mohit,
Yeah, those are great places to go and learn.
To fill in a bit more on this topic: "partition-tolerance" usually refers to
the idea that you could have a complete disconnection between N sets of
machines in your data center, but still be taking writes and serving reads from
all the serv
Get the HBase book:
http://www.amazon.com/HBase-Definitive-Guide-Lars-George/dp/1449396100
And/Or read the Bigtable paper.
J-D
On Fri, Dec 2, 2011 at 12:01 PM, Mohit Anchlia wrote:
> Where can I read more on this specific subject?
>
> Based on your answer I have more questions, but I want to re
Where can I read more on this specific subject?
Based on your answer I have more questions, but I want to read more
specific information about how it works and why it's designed that
way.
On Fri, Dec 2, 2011 at 11:59 AM, Jean-Daniel Cryans wrote:
> No, data is only served by one region server (e
No, data is only served by one region server (even if it resides on
multiple data nodes). If it dies, clients need to wait for the log
replay and region reassignment.
J-D
On Fri, Dec 2, 2011 at 11:57 AM, Mohit Anchlia wrote:
> Why is HBase consisdered high in consistency and that it gives up
> p
Why is HBase consisdered high in consistency and that it gives up
parition tolerance? My understanding is that failure of one data node
still doesn't impact client as they would re-adjust the list of
available data nodes.
10 matches
Mail list logo
