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-8879) Client Scanner spams the logs if there are lots of scanners.
Date Fri, 05 Jul 2013 23:33:48 GMT

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

Hadoop QA commented on HBASE-8879:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12591046/HBASE-8879-0.patch
  against trunk revision .

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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 2 warning messages.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 findbugs{color}.  The patch does not introduce any 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:green}+1 site{color}.  The mvn site goal succeeds with this patch.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/6227//console

This message is automatically generated.
                
> Client Scanner spams the logs if there are lots of scanners.
> ------------------------------------------------------------
>
>                 Key: HBASE-8879
>                 URL: https://issues.apache.org/jira/browse/HBASE-8879
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.98.0, 0.95.1
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>              Labels: noob
>         Attachments: HBASE-8879-0.patch
>
>
> The log in client scanner should probably be on the trace level otherwise you end up
with this:
> {code}
> 2013-07-05 12:41:12,501 DEBUG [pool-48-thread-3] client.ClientScanner(97): Scan table=IntegrationTestMTTR,
startRow=
> 2013-07-05 12:41:12,502 DEBUG [pool-48-thread-3] client.ClientScanner(97): Scan table=IntegrationTestMTTR,
startRow=
> 2013-07-05 12:41:12,503 DEBUG [pool-48-thread-3] client.ClientScanner(97): Scan table=IntegrationTestMTTR,
startRow=
> 2013-07-05 12:41:12,506 DEBUG [pool-48-thread-3] client.ClientScanner(97): Scan table=IntegrationTestMTTR,
startRow=
> 2013-07-05 12:41:12,507 DEBUG [pool-48-thread-3] client.ClientScanner(97): Scan table=IntegrationTestMTTR,
startRow=
> 2013-07-05 12:41:12,508 DEBUG [pool-48-thread-3] client.ClientScanner(97): Scan table=IntegrationTestMTTR,
startRow=
> 2013-07-05 12:41:12,509 DEBUG [pool-48-thread-3] client.ClientScanner(97): Scan table=IntegrationTestMTTR,
startRow=
> 2013-07-05 12:41:12,509 DEBUG [pool-48-thread-3] client.ClientScanner(97): Scan table=IntegrationTestMTTR,
startRow=
> 2013-07-05 12:41:12,510 DEBUG [pool-48-thread-3] client.ClientScanner(97): Scan table=IntegrationTestMTTR,
startRow=
> {code}

--
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

Mime
View raw message