[
https://issues.apache.org/jira/browse/HBASE-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863590#comment-13863590
]
Enis Soztutar commented on HBASE-10241:
---------------------------------------
bq. but the plan was that I will do 1 and 3, and then take 2 if the other JIRA
that does 2 is not done by then.
Sounds good. I thought HBASE-8721 is won't fix.
bq. HBASE-8763 does not need to block this, it's probably bigger than this
entire JIRA
Indeed. But it will be a shame if we add mvcc's to WAL only to remove them
again after HBASE-8763.
BTW, I think we also have to handle mvcc / seqId as a part of the serialization
in the KV byte array. Do we have any open issues for that?
> implement mvcc-consistent scanners (across recovery)
> ----------------------------------------------------
>
> Key: HBASE-10241
> URL: https://issues.apache.org/jira/browse/HBASE-10241
> Project: HBase
> Issue Type: New Feature
> Components: HFile, regionserver, Scanners
> Affects Versions: 0.99.0
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: Consistent scanners.pdf
>
>
> Scanners currently use mvcc for consistency. However, mvcc is lost on server
> restart, or even a region move. This JIRA is to enable the scanners to
> transfer mvcc (or seqId, or some other number, see HBASE-8763) between
> servers. First, client scanner needs to get and store the readpoint. Second,
> mvcc needs to be preserved in WAL. Third, the mvcc needs to be stored in
> store files per KV and discarded when not needed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
