[
https://issues.apache.org/jira/browse/HBASE-13883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064893#comment-15064893
]
Hadoop QA commented on HBASE-13883:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12778549/HBASE-13883.patch
against master branch at commit ba04e0372da560715bb4b1aa329c0091764340ea.
ATTACHMENT ID: 12778549
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.6.1 2.7.0
2.7.1)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not generate new
checkstyle errors.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) 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:green}+1 site{color}. The mvn post-site goal succeeds with this
patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
{color:green}+1 zombies{color}. No zombie tests found running at the end of
the build.
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/16929//testReport/
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/16929//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/16929//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/16929//console
This message is automatically generated.
> Fix Memstore Flush section in HBase book
> ----------------------------------------
>
> Key: HBASE-13883
> URL: https://issues.apache.org/jira/browse/HBASE-13883
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Affects Versions: 2.0.0
> Reporter: Vladimir Rodionov
> Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-13883.patch
>
>
> {quote}
> 65.7.2. MemStore Flush
> A MemStore flush can be triggered under any of the conditions listed below.
> The minimum flush unit is per region, not at individual MemStore level.
> // SKIPPED
> 3. When the number of WAL per region server reaches the value specified
> in hbase.regionserver.max.logs, MemStores from various regions will be
> flushed out to disk to reduce WAL count. The flush order is based on time.
> Regions with the oldest MemStores are flushed first until WAL count drops
> below hbase.regionserver.max.logs.
> {quote}
> Section 3. requires clarification (reference to HBase version which supports
> this). Is it MultiWAL feature in 1.0?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
