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-8359) Too much logs on HConnectionManager
Date Wed, 17 Apr 2013 20:21:17 GMT

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

Hadoop QA commented on HBASE-8359:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12579159/8359.v1.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 hadoop2.0{color}.  The patch compiles against the hadoop 2.0 profile.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 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/5335//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5335//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5335//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5335//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5335//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5335//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5335//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5335//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5335//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/5335//console

This message is automatically generated.
                
> Too much logs on HConnectionManager
> -----------------------------------
>
>                 Key: HBASE-8359
>                 URL: https://issues.apache.org/jira/browse/HBASE-8359
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.95.0
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>         Attachments: 8359.v1.patch
>
>
> Under a YCSB load test (for HBASE-6295), we can have sporadic bulk of logs because of
this:
> {code}
>       final RegionMovedException rme = RegionMovedException.find(exception);
>       if (rme != null) {
>         LOG.info("Region " + regionInfo.getRegionNameAsString() + " moved to " +
>           rme.getHostname() + ":" + rme.getPort() + " according to " + source.getHostnamePort());
>         updateCachedLocation(
>             regionInfo, source, rme.getServerName(), rme.getLocationSeqNum());
>       } else if (RegionOpeningException.find(exception) != null) {
>         LOG.info("Region " + regionInfo.getRegionNameAsString() + " is being opened on
"
>           + source.getHostnamePort() + "; not deleting the cache entry");
>       } else {
>         deleteCachedLocation(regionInfo, source);
>       }
> {code}
> They should just be removed.

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