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-13831) TestHBaseFsck#testParallelHbck is flaky
Date Wed, 03 Jun 2015 21:30:40 GMT

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

Hadoop QA commented on HBASE-13831:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12737346/HBASE-13831.patch
  against master branch at commit fad545652fc330d11061a1608e7812dade7f0845.
  ATTACHMENT ID: 12737346

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
tests.

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions
(2.4.1 2.5.2 2.6.0)

    {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 increase the total number
of 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 site goal succeeds with this patch.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/14270//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/14270//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/14270//artifact/patchprocess/checkstyle-aggregate.html

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

This message is automatically generated.

> TestHBaseFsck#testParallelHbck is flaky
> ---------------------------------------
>
>                 Key: HBASE-13831
>                 URL: https://issues.apache.org/jira/browse/HBASE-13831
>             Project: HBase
>          Issue Type: Bug
>          Components: hbck, test
>    Affects Versions: 2.0.0, 1.1.0, 1.2.0
>            Reporter: Stephen Yuan Jiang
>            Assignee: Stephen Yuan Jiang
>            Priority: Minor
>             Fix For: 2.0.0, 1.2.0, 1.1.1
>
>         Attachments: HBASE-13831.patch
>
>
> Running TestHBaseFsck#testParallelHbck is flaky against HADOOP-2.6+ environment.  The
idea of the test is that with when 2 HBCK operations are running simultaneously, the 2nd HBCK
would fail with no-retry because creating lock file would fail due to the 1st HBCK already
created.  However, with HADOOP-2.6+, the FileSystem#createFile call internally retries with
AlreadyBeingCreatedException (see HBASE-13574 for more details: "It seems that test is broken
due of the new create retry policy in hadoop 2.6. Namenode proxy now created with custom RetryPolicy
for AlreadyBeingCreatedException which is implies timeout on this operations up to HdfsConstants.LEASE_SOFTLIMIT_PERIOD
(60seconds).")
> When I run the TestHBaseFsck#testParallelHbck test against HADOOP-2.7 in a Windows environment
(HBASE is branch-1.1) multiple times, the result is unpredictable (sometime succeeded, sometime
failed - more failure than succeeded).  
> The fix is trivial: Leverage the change in HBASE-13732 and reduce the max wait time to
a smaller number.   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message