hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15082) Fix merge of MVCC and SequenceID performance regression
Date Tue, 12 Jan 2016 18:48:39 GMT

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

stack commented on HBASE-15082:
-------------------------------

Removed 1.2.0 as target. [~eclark] in reivew found flaw. I have updates completing mvcc only
rather than completing AND waiting on mvcc transaction to catch up. Means no guarantee that
you can read your own writes. Need to go back to perf test before making progress here. Means
for sure doesn't make 1.2.0. I opened HBASE-15091 to do forward-port of the branch-1 patch
(though HBASE-12751 changes the landscape).



> Fix merge of MVCC and SequenceID performance regression
> -------------------------------------------------------
>
>                 Key: HBASE-15082
>                 URL: https://issues.apache.org/jira/browse/HBASE-15082
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Performance
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0, 1.3.0
>
>         Attachments: 15082.patch, 15082v10.patch, 15082v2.patch, 15082v2.txt, 15082v3.txt,
15082v4.patch, 15082v5.patch, 15082v6.patch, 15082v7.patch, 15082v8.patch
>
>
> This is general fix for increments (appends, checkAnd*) perf-regression identified in
the parent issue. HBASE-15031 has a narrow fix for branch-1.1 and branch-1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message