[
https://issues.apache.org/jira/browse/HBASE-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688839#comment-13688839
]
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/12588745/HBASE-8541-latest-with-dependencies.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 51 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6080//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: Improvement
> Reporter: Sergey Shelukhin
> Attachments: HBASE-8541-latest-with-dependencies.patch,
> HBASE-8541-latest-with-dependencies.patch, HBASE-8541-v0.patch,
> HBASE-8541-v1.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
