[
https://issues.apache.org/jira/browse/HBASE-14465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-14465:
--------------------------------
Release Note:
Locks on row are now reader/writer rather than exclusive.
Moves sequenceid out of HRegion and into MVCC class; MVCC is now in charge. A
WAL append is still stamped in same way (we pass MVCC context in a few places
where we previously we did not).
MVCC methods cleaned up. Make a bit more sense now. Less of them.
Simplifies our update of MemStore/WAL. Now we update memstore AFTER we add to
WAL (but before we sync). This fixes possible dataloss when two edits came in
with same coordinates; we could order the edits in memstore differently to how
they arrived in the WAL.
Marked as an incompatible change because it breaks Distributed Log Replay, a
feature we'd determined already was unreliable and to be removed (See
http://search-hadoop.com/m/YGbbhTJpoal8GD1).
was:See parent issue.
> Backport 'Allow rowlock to be reader/write' to branch-1
> -------------------------------------------------------
>
> Key: HBASE-14465
> URL: https://issues.apache.org/jira/browse/HBASE-14465
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver
> Reporter: stack
> Assignee: stack
> Fix For: 1.2.0, 1.3.0
>
> Attachments: 14465.branch-1.txt, 14465.branch-1.v2.txt,
> 14465.branch-1.v2.txt, 14465.branch-1.v2.txt, 14465.branch-1.v3.txt,
> 14465.branch-1.v3.txt, 14465.branch-1.v4.txt, 14465.branch-1.v4.txt,
> 14465.branch-1.v4.txt, 14465.branch-1.v5.txt, 14465.branch-1.v5.txt,
> 14465.branch-1.v9.txt, 14465.branch-1.v9.txt, 14465.branch-1.v9.txt, 14465.txt
>
>
> Backport to branch-1.
> You want this in 1.2 [~busbey]? Its cleanup and fixes a possible dataloss. On
> other hand, its a bit of refactoring.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
