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

Hadoop QA commented on HBASE-4300:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12494701/4300-v2.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 9 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

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

This message is automatically generated.
                
> Start of new-version master fails if old master's znode is hanging around
> -------------------------------------------------------------------------
>
>                 Key: HBASE-4300
>                 URL: https://issues.apache.org/jira/browse/HBASE-4300
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.92.0
>
>         Attachments: 4300-v2.txt, 4300.txt
>
>
> I shut down an 0.90 cluster, and had to do so uncleanly. I then started a 
> trunk (0.92) cluster before the old master znode had expired. This cased:
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>         at java.lang.String.substring(String.java:1937)
>         at 
> org.apache.hadoop.hbase.ServerName.parseHostname(ServerName.java:81)
>         at org.apache.hadoop.hbase.ServerName.<init>(ServerName.java:63)
>         at 
> org.apache.hadoop.hbase.master.ActiveMasterManager.blockUntilBecomingActiveMaster(ActiveMasterManager.java:148)
>         at 
> org.apache.hadoop.hbase.master.HMaster.becomeActiveMaster(HMaster.java:342)
>         at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:297)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to