Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 19C22C9E9 for ; Thu, 3 May 2012 18:27:22 +0000 (UTC) Received: (qmail 22209 invoked by uid 500); 3 May 2012 18:27:20 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 22145 invoked by uid 500); 3 May 2012 18:27:20 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 22137 invoked by uid 99); 3 May 2012 18:27:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2012 18:27:20 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.160.169 as permitted sender) Received: from [209.85.160.169] (HELO mail-gy0-f169.google.com) (209.85.160.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2012 18:27:15 +0000 Received: by ghrr18 with SMTP id r18so2944122ghr.14 for ; Thu, 03 May 2012 11:26:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=NIbchYJAaUf6VQ+p8qbSZVgmJqv+U3IMYyVXxPvmi8A=; b=CpgrU8R4qalhxOehBHnPD7XmW2A5gHjEHXaVx7cv1zvDRNpaI7lMLmLEvQtddj4qcI zxoNFgva5eksfohdMAvgvqize2ZubYCp1srzrweA5kTx1s2pAVRb0fgaB51Zk98oKwc4 /ASE3tIdGza0tNwX5lE7KxrhLKEAN4IXJ5PVQfa2tl3tL+hle/Br+iPgFwqalw0h45qC J66Bjfrnlgmee/fUyACyNwUjGgAOQQ9FGrb7Yv8GhbAp3kNdU3Xqj6MmpaD13ZPim0O5 jCNWqfGi+aYQuMHWwUEO3zqR6WKFL/6KUsE72m5kf8wyuTCg+2MGyXOtGZ3uTfOByl8X WpXg== MIME-Version: 1.0 Received: by 10.236.168.42 with SMTP id j30mr4211726yhl.25.1336069614413; Thu, 03 May 2012 11:26:54 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.100.40.7 with HTTP; Thu, 3 May 2012 11:26:54 -0700 (PDT) In-Reply-To: References: Date: Thu, 3 May 2012 11:26:54 -0700 X-Google-Sender-Auth: Lc6NM69gz2mqtheRBK9FRNWYXAU Message-ID: Subject: Re: multi-data center support From: Jean-Daniel Cryans To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org A single HBase instance doesn't work across datacenters, maybe that's why you haven't found any documentation. HBase does have replication between clusters, see http://hbase.apache.org/replication.html J-D On Thu, May 3, 2012 at 11:10 AM, Marco Villalobos wrote: > I have not found any documentation on how hbase would work across > multiple data-centers. > > In fact, I am concerned about how a centralized zookeeper would make > multi-data center support impossible. > > How is this handled? =A0What if somebody needs to read and write from > multiple data-centers? > > Any advice?