[
https://issues.apache.org/jira/browse/HBASE-15451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203062#comment-15203062
]
Hudson commented on HBASE-15451:
--------------------------------
SUCCESS: Integrated in HBase-1.3-IT #567 (See
[https://builds.apache.org/job/HBase-1.3-IT/567/])
HBASE-15451 Remove unnecessary wait in MVCC (liyu: rev
463374ecfa770645c7098b4648cb805933eb7aab)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MultiVersionConcurrencyControl.java
> 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.3.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)
