[
https://issues.apache.org/jira/browse/HBASE-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808307#comment-13808307
]
Hadoop QA commented on HBASE-8541:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12610867/HBASE-8541-v4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 8
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7664//console
This message is automatically generated.
> implement flush-into-stripes in stripe compactions
> --------------------------------------------------
>
> Key: HBASE-8541
> URL: https://issues.apache.org/jira/browse/HBASE-8541
> Project: HBase
> Issue Type: Sub-task
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HBASE-8541-latest-with-dependencies.patch,
> HBASE-8541-latest-with-dependencies.patch,
> HBASE-8541-latest-with-dependencies.patch,
> HBASE-8541-latest-with-dependencies.patch, HBASE-8541-v0.patch,
> HBASE-8541-v1.patch, HBASE-8541-v2.patch, HBASE-8541-v3.patch,
> HBASE-8541-v4.patch
>
>
> Flush will be able to flush into multiple files under this design, avoiding
> L0 I/O amplification.
> I have the patch which is missing just one feature - support for concurrent
> flushes and stripe changes. This can be done via extensive try-locking of
> stripe changes and flushes, or advisory flags without blocking flushes,
> dumping conflicting flushes into L0 in case of (very rare) collisions. For
> file loading for the latter, a set-cover-like problem needs to be solved to
> determine optimal stripes. That will also address Jimmy's concern of getting
> rid of metadata, btw. However currently I don't have time for that. I plan to
> attach the try-locking patch first, but this won't happen for a couple weeks
> probably and should not block main reviews. Hopefully this will be added on
> top of main reviews.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
