You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mikhail Antonov (JIRA)" <ji...@apache.org> on 2016/06/20 19:01:00 UTC
[jira] [Commented] (HBASE-15451) Remove unnecessary wait in MVCC
[ https://issues.apache.org/jira/browse/HBASE-15451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340183#comment-15340183 ]
Mikhail Antonov commented on HBASE-15451:
-----------------------------------------
Seems like Hudson mis-reporting the branchs stuff was integrated in, 1.3-IT shouldn't have been show up here. Marking fixVer as 1.4.
> Remove unnecessary wait in MVCC
> -------------------------------
>
> Key: HBASE-15451
> URL: https://issues.apache.org/jira/browse/HBASE-15451
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.0.0, 1.2.0
> Reporter: Yu Li
> Assignee: Yu Li
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-15451.patch, HBASE-15451.test
>
>
> Currently the return value of MVCC#complete indicates whether readPoint already advanced over write number of the given WriteEntry:
> {code}
> return readPoint.get() >= writeEntry.getWriteNumber();
> {code}
> While in MVCC#checkAndWait we never take usage of this but always call waitForRead which will acquire and release lock on {{readWaiters}} and cause additional context switch. This JIRA will improve this logic and remove the unnecessary wait.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)