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-13129) Add troubleshooting hints around WAL retention from replication
Date Sat, 19 Dec 2015 00:42:46 GMT

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

Hadoop QA commented on HBASE-13129:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  against master branch at commit eb59d4d7690bb4d8d0afa460202c68885ef6a271.
  ATTACHMENT ID: 12778578

    {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

    {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/16933//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/16933//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/16933//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/16933//console

This message is automatically generated.

> Add troubleshooting hints around WAL retention from replication
> ---------------------------------------------------------------
>                 Key: HBASE-13129
>                 URL: https://issues.apache.org/jira/browse/HBASE-13129
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation, Replication
>            Reporter: Sean Busbey
>            Assignee: Misty Stanley-Jones
>              Labels: operations, supportability
>         Attachments: HBASE-13129.patch
> There's been some confusion on the mailing list about when WALs get retained  / cleaned
up once replication is on at all in a cluster. (ref [this thread|http://mail-archives.apache.org/mod_mbox/hbase-user/201502.mbox/%3CCAMUu0w9aOVBo7kGULiM9tXrULirqs9fm-3ra3pQccYpW_17uOw@mail.gmail.com%3E])
> We should add a NOTE in the replication section that wals are saved across enable/disable
so long as there are peers. There looks like there might also be some confusing language around
replication being enabled in the configs vs the enable/disable suspension mechanism.
> We should also add a troubleshooting item specific for "my HDFS space keeps growing and
it's all in oldWALs."

This message was sent by Atlassian JIRA

View raw message