Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of ivarley@salesforce.com
 designates 64.18.3.92 as permitted sender)
From: Ian Varley <ivarley@salesforce.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Date: Fri, 7 Dec 2012 10:19:25 -0800
Subject: Re: PROD/DR - Replication
Thread-Topic: PROD/DR - Replication
Thread-Index: Ac3Up21dQe5o5TFTROabwJMpConuag==
Message-ID: <78D549B8-F222-412D-8B28-EC6F713A6631@salesforce.com>
References: 
 <CAD8ZxGpGG19uD2HpOyw2igEHD+HAwZ0hViNPg=Uy8YOnbpx19Q@mail.gmail.com>
In-Reply-To: 
 <CAD8ZxGpGG19uD2HpOyw2igEHD+HAwZ0hViNPg=Uy8YOnbpx19Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_78D549B8F222412D8B28EC6F713A6631salesforcecom_"
MIME-Version: 1.0

--_000_78D549B8F222412D8B28EC6F713A6631salesforcecom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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 dramati=
cally. 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


--_000_78D549B8F222412D8B28EC6F713A6631salesforcecom_--