PROD/DR - Replication

2012-12-07 Thread Andrew Purtell
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 varia

Re: PROD/DR - Replication

2012-12-07 Thread Ian Varley
:ivar...@salesforce.com>> To: "user@hbase.apache.org<mailto:user@hbase.apache.org>" mailto:user@hbase.apache.org>> Sent: Saturday, 8 December 2012, 1:21 Subject: Re: PROD/DR - Replication Yes, I think so. A single HBase cluster can't (or, at least, really shouldn'

Re: PROD/DR - Replication

2012-12-07 Thread sriraam h
Thanks Ian. I DID miss the point. The person who started the chain is a different person :) - Sri > > From: Ian Varley >To: "user@hbase.apache.org" >Sent: Saturday, 8 December 2012, 1:21 >Subject: Re: PROD/DR - Replication > >

Re: PROD/DR - Replication

2012-12-07 Thread Amandeep Khurana
What failure condition are you trying to safeguard against? A full data center failure? That's when you would lose your entire cluster and need the DR to kick in. Otherwise, you could deploy such that an entire rack failure or even a row failure won't take you down. Just span across multiple racks

Re: PROD/DR - Replication

2012-12-07 Thread Ian Varley
uch as high-speed counter > aggregation" > > http://hbase.apache.org/book/architecture.html > > > Am I missing something ? > > - Sri > > > >> >> From: Ian Varley >> To: "user@hbase.apache.org" >&g

Re: PROD/DR - Replication

2012-12-07 Thread sriraam h
___ > From: Ian Varley >To: "user@hbase.apache.org" >Sent: Friday, 7 December 2012, 23:49 >Subject: Re: PROD/DR - Replication > >Juan, > >No; that would mean every single write to HBase has to wait for an ACK from a >remote data center, which would

Re: PROD/DR - Replication

2012-12-07 Thread Ian Varley
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 Rep

PROD/DR - Replication

2012-12-07 Thread Juan P.
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