Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> HBase and Consistency in CAP


Copy link to this message
-
Re: HBase and Consistency in CAP
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 <[EMAIL PROTECTED]> wrote:
> 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 <[EMAIL PROTECTED]> wrote:
>> 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.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB