Consistency between replicated clusters (across data centers) is asynchronous and can also be considered "eventual". From within a single cluster, only a single node is responsible for serving a given range of data, so there is only one, consistent, view on that data. This model can be relaxed via configuration with the introduction of HBASE-10070.
On Friday, March 14, 2014, lars hofhansl <[email protected]> wrote: > Might be best to look up the "CAP theorem". In that terms HBase is a CP > store (consistent and partition tolerant). > HBase will probably provide some eventual consistency soon via HBASE-10070. > > > -- Lars > > > > ________________________________ > From: Vimal Jain <[email protected] <javascript:;>> > To: "[email protected] <javascript:;>" > <[email protected]<javascript:;> > > > Sent: Friday, March 14, 2014 12:02 AM > Subject: Re: Eventual consistency in Hbase > > > You mean Hbase is not an "eventual consistent" ? > Then what kind of consistency it provides ? > Where can i get more information about different consistency models ? > > > On Fri, Mar 14, 2014 at 12:26 PM, Salabhanjika S > <[email protected]<javascript:;> > >wrote: > > > https://hbase.apache.org/book/architecture.html > > > > "Strongly consistent reads/writes: HBase is not an "eventually > > consistent" DataStore. This makes it very suitable for tasks such as > > high-speed counter aggregation." > > > > On Fri, Mar 14, 2014 at 12:21 PM, Vimal Jain > > <[email protected]<javascript:;>> > wrote: > > > Hi, > > > I heard that Hbase provides eventual consistency. > > > What does that mean ? > > > Where can i get more information on different consistency model and how > > > hbase achieves eventual consistency ? > > > > > > -- > > > Thanks and Regards, > > > Vimal Jain > > > > > > -- > Thanks and Regards, > Vimal Jain
