Return-Path: 
 <issues-return-24044-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 B7C459E79
	for <apmail-hbase-issues-archive@www.apache.org>;
 Wed,  2 Nov 2011 17:49:56 +0000 (UTC)
Received: (qmail 5670 invoked by uid 500); 2 Nov 2011 17:49:56 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 5643 invoked by uid 500); 2 Nov 2011 17:49:56 -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 5596 invoked by uid 99); 2 Nov 2011 17:49:56 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Nov 2011 17:49:56 +0000
X-ASF-Spam-Status: No, hits=-2001.2 required=5.0
	tests=ALL_TRUSTED,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; Wed, 02 Nov 2011 17:49:54 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 3166732E6BD
	for <issues@hbase.apache.org>; Wed,  2 Nov 2011 17:49:33 +0000 (UTC)
Date: Wed, 2 Nov 2011 17:49:33 +0000 (UTC)
From: "Jonathan Hsieh (Updated) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1788343193.51458.1320256173203.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 ]

Jonathan Hsieh updated HBASE-3903:
----------------------------------

    Fix Version/s: 0.92.0
    
> 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
>             Fix For: 0.92.0
>
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira