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

Hadoop QA commented on HBASE-5582:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12548008/HBASE-5582.patch1
  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:red}-1 javadoc{color}.  The javadoc tool appears to have generated 
81 warning messages.

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

    {color:red}-1 findbugs{color}.  The patch appears to introduce 5 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 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3014//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3014//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3014//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3014//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3014//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3014//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3014//console

This message is automatically generated.
                
> "No HServerInfo found for" should be a WARNING message
> ------------------------------------------------------
>
>                 Key: HBASE-5582
>                 URL: https://issues.apache.org/jira/browse/HBASE-5582
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.90.4
>            Reporter: Shrijeet Paliwal
>            Assignee: Kevin Odell
>            Priority: Trivial
>              Labels: newbie
>             Fix For: 0.96.0
>
>         Attachments: HBASE-5582.patch, HBASE-5582.patch1
>
>
> The message from RegionServerTracker "No HServerInfo found for..." is easy to 
> miss. It should not be INFO. 
> From irc chat 
> {noformat}
> jdcryans
> JohnP789: can you grep for "No HServerInfo found for" in that log?
> jdcryans
> wait I see it
> jdcryans
> ok there's your problem
> shrijeet_
> Yes it is there
> shrijeet_
> jdcryans: it should be INFO, why?
> jdcryans
> it shouldn't be INFO, it's so easy to miss
> jdcryans
> it's not the first time we have to look super closely to figure this one out
> shrijeet_
> yes , I will file a jira
> jdcryans
> in any case it's a mismatch in that machine's DNS config
> shrijeet_
> anyways JohnP789 is waiting :) go on
> JohnP789
> haha!
> JohnP789
> yes...  ???  :-)
> jdcryans
> the master is expecting a RS called 
> "localhost.localdomain,53875,1328924863478"
> 17:26 jdcryans
> but the RS calls itself "localhost,53875,1328924863478"
> {noformat}

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

Reply via email to