Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 16 Jan 2012 18:49:40 +0000 (UTC)
From: "Lars Hofhansl (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1401036427.45494.1326739780266.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1088859338.43192.1326667539792.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5203) Group atomic put/delete operation
 into a single WALEdit to handle region server failures.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187074#comment-13187074 ] 

Lars Hofhansl commented on HBASE-5203:
--------------------------------------

@Ram: I see what you mean. Good point.
Unlike doMiniBatchPut there is no partial completion here, but the postHooks should indeed only be run if the (entire) operation was successful. I'll have a change soon.

                
> Group atomic put/delete operation into a single WALEdit to handle region server failures.
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-5203
>                 URL: https://issues.apache.org/jira/browse/HBASE-5203
>             Project: HBase
>          Issue Type: Sub-task
>          Components: client, coprocessors, regionserver
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.94.0
>
>         Attachments: 5203.txt
>
>
> HBASE-3584 does not not provide fully atomic operation in case of region server failures (see explanation there).
> What should happen is that either (1) all edits are applied via a single WALEdit, or (2) the WALEdits are applied in async mode and then sync'ed together.
> For #1 it is not clear whether it is advisable to manage multiple *different* operations (Put/Delete) via a single WAL edit. A quick check reveals that WAL replay on region startup would work, but that replication would need to be adapted. The refactoring needed would be non-trivial.
> #2 Might actually not work, as another operation could request sync'ing a later edit and hence flush these entries out as well.

--
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