Return-Path: 
 <issues-return-12803-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-issues-archive@www.apache.org
Delivered-To: apmail-hbase-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 01D4C6D93
	for <apmail-hbase-issues-archive@www.apache.org>;
 Fri, 20 May 2011 20:10:31 +0000 (UTC)
Received: (qmail 50773 invoked by uid 500); 20 May 2011 20:10:30 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 50752 invoked by uid 500); 20 May 2011 20:10:30 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 50682 invoked by uid 99); 20 May 2011 20:10:30 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 May 2011 20:10:30 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 May 2011 20:10:28 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id D08E8D471B
	for <issues@hbase.apache.org>; Fri, 20 May 2011 20:09:47 +0000 (UTC)
Date: Fri, 20 May 2011 20:09:47 +0000 (UTC)
From: "Doug Meil (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1095076519.31791.1305922187851.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <997026794.28792.1305845147389.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-3903) A successful write to client
 write-buffer may be lost or not visible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/HBASE-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Meil updated HBASE-3903:
-----------------------------

    Attachment: book_HBASE_3903.xml.patch

> A successful write to client write-buffer may be lost or not visible
> --------------------------------------------------------------------
>
>                 Key: HBASE-3903
>                 URL: https://issues.apache.org/jira/browse/HBASE-3903
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>         Environment: Any.
>            Reporter: Tallat
>            Assignee: Doug Meil
>            Priority: Minor
>              Labels: documentation
>         Attachments: acid-semantics_HBASE_3903.xml.patch, book_HBASE_3903.xml.patch
>
>
> A client can do a write to a client side 'write buffer' if enabled via hTable.setAutoFlush(false). Now, assume a client puts value v under key k. Two wrongs things can happen, violating the ACID semantics  of Hbase given at: http://hbase.apache.org/acid-semantics.html
> 1) Say the client fails immediately after the put succeeds. In this case, the put will be lost, violating the durability property:
> <quote> Any operation that returns a "success" code (eg does not throw an exception) will be made durable. </quote>
>  
> 2) Say the client issues a read for k immediately after writing k. The put will be stored in the client side write buffer, while the read will go to the region server, returning an older value, instead of v, violating the visibility property:
> <quote>
> When a client receives a "success" response for any mutation, that mutation
> is immediately visible to both that client and any client with whom it later
> communicates through side channels.
> </quote>
> Thanks,
> Tallat

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira