Agree with what Ian says below except I'd say with work it's possible to do cross DC quorum writes in a layer on top of HBase that persists into HBase, like when Google built Megastore on BigTable. At this year's VLDB if I recall correctly there was a megastore-like system with an interesting variation built on HBase presented in http://arxiv.org/abs/1208.0270 .
On Saturday, December 8, 2012, Ian Varley wrote: > Juan, > > No; that would mean every single write to HBase has to wait for an ACK > from a remote data center, which would decrease your cluster throughput > dramatically. If you need that, consider other database solutions. > > Ian > > On Dec 7, 2012, at 12:14 PM, Juan P. wrote: > > I was reading up on HBase Replication and wanted to make sure I'm not > missing something. > > Given that replication happens asynchronously the replication strategy has > an "eventually consistent" policy. > > I was considering using this feature for Production / Disaster Recovery > setup. > > Is there a way to enforce Consistency so that if my PROD environment should > ever go down, I can 100% sure that DR will be completely up to date? > > Thank you, > Juan > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
