Return-Path: Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: (qmail 75512 invoked from network); 31 May 2010 07:32:11 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 31 May 2010 07:32:11 -0000 Received: (qmail 38340 invoked by uid 500); 31 May 2010 07:32:11 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 38248 invoked by uid 500); 31 May 2010 07:32:09 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 38235 invoked by uid 500); 31 May 2010 07:32:08 -0000 Delivered-To: apmail-hadoop-hbase-dev@hadoop.apache.org Received: (qmail 38231 invoked by uid 99); 31 May 2010 07:32:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 May 2010 07:32:08 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shiyingjie1983@gmail.com designates 209.85.211.171 as permitted sender) Received: from [209.85.211.171] (HELO mail-yw0-f171.google.com) (209.85.211.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 May 2010 07:31:59 +0000 Received: by ywh1 with SMTP id 1so2454674ywh.22 for ; Mon, 31 May 2010 00:31:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=AmxlWub1WRqhFlJ02fT4acn4RhB4tHTSBMFDY7Cpa3I=; b=R/mDim8OXw+nTLrvNe3nl2mnnx9MTthdBfxTLDXGRiu7LXBISv32vtOvQvQybL/PcM G+vPcHJE/DSXn8rJhYzrJgtPY9kv7y+8ta0f/N9RldYUNOfQ3Hf6CZy4xhM1nxWUj90o p810R4IlBDp0H26dugvUFEsrvxv2Vl8FmsDfs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=cz/QGGd+v033cBICGQvY5L9Kcfw2A9ncQpPIBha0v2siHd980rBTACE+RZtogPA4/j N85pRmhGdFWNvw6yRNYGBst9dtj2mc6qNfLBTgKc9ipmEKDf1xUXSTqEFE0Uk2zXsDYE qOw1gzcCyea3Bojyv/g0+Wvf++zkiH1ZoKK2o= MIME-Version: 1.0 Received: by 10.101.133.30 with SMTP id k30mr4352743ann.42.1275291098456; Mon, 31 May 2010 00:31:38 -0700 (PDT) Received: by 10.100.105.20 with HTTP; Mon, 31 May 2010 00:31:38 -0700 (PDT) Date: Mon, 31 May 2010 15:31:38 +0800 Message-ID: Subject: Does HBase support strong consistency? From: =?GB2312?B?yrfTor3c?= To: hbase-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e68ef470e8a1f40487ded8c7 X-Virus-Checked: Checked by ClamAV on apache.org --0016e68ef470e8a1f40487ded8c7 Content-Type: text/plain; charset=ISO-8859-1 Hi, All I learned from some forums that HBase focuses CA, which are two properties in CAP. Does HBase support strong consistency in the data replicas, which mechanism does it use to guarantee consistency? Thanks a lot! Yingjie --0016e68ef470e8a1f40487ded8c7--