You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Himanshu Vashishtha (JIRA)" <ji...@apache.org> on 2013/03/07 19:34:13 UTC

[jira] [Commented] (HBASE-8028) Append, Increment don't handle wall-sync exceptions correctly

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

Himanshu Vashishtha commented on HBASE-8028:
--------------------------------------------

I think we can make use of the local tempMemStore map variable to store the existing KVs, and rather apply the incoming appends, etc in-place (before applying them to the WAL). Those entries will not be visible for read as long as are not moving the mvcc forward, so it should be ok. 
Now, in case there is an exception, we can restore the previous values from the tempMemstore map. Thoughts on other approaches?
                
> Append, Increment don't handle wall-sync exceptions correctly
> -------------------------------------------------------------
>
>                 Key: HBASE-8028
>                 URL: https://issues.apache.org/jira/browse/HBASE-8028
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.94.5
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>             Fix For: 0.95.0
>
>
> In case there is an exception while doing the log-sync, the memstore is not rollbacked, while the mvcc is _always_ forwarded to the writeentry created at the beginning of the operation. This may lead to scanners seeing results which are not synched to the fs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira