hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15451) Remove unnecessary wait in MVCC
Date Sun, 13 Mar 2016 11:40:33 GMT

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

Hadoop QA commented on HBASE-15451:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m 1s {color} | {color:blue}
The patch file was not named according to hbase's naming conventions. Please see https://yetus.apache.org/documentation/0.2.0/precommit-patchnames
for instructions. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 10m 50s {color} | {color:red}
Docker failed to build yetus/hbase:date2016-03-13. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12793194/HBASE-15451.test
|
| JIRA Issue | HBASE-15451 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/947/console |
| Powered by | Apache Yetus 0.2.0   http://yetus.apache.org |


This message was automatically generated.



> 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
>         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)

Mime
View raw message