[
https://issues.apache.org/jira/browse/HBASE-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165009#comment-13165009
]
Hudson commented on HBASE-4610:
-------------------------------
Integrated in HBase-0.92-security #33 (See
[https://builds.apache.org/job/HBase-0.92-security/33/])
HBASE-4610 Addendum removes break statement
HBASE-4610 Port HBASE-3380 (Master failover can split logs of live servers) to
92/trunk
tedyu :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/ServerManager.java
tedyu :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/ServerManager.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java
> Port HBASE-3380 (Master failover can split logs of live servers) to 92/trunk
> (definitely bring in config params, decide if we need to do more to fix the
> bug)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-4610
> URL: https://issues.apache.org/jira/browse/HBASE-4610
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.92.0, 0.94.0
> Reporter: Jonathan Gray
> Assignee: Jonathan Gray
> Fix For: 0.92.0, 0.94.0
>
> Attachments: 4610.txt
>
>
> Over in HBASE-3380 we were having some TestMasterFailover flakiness. We
> added some more config parameters to better control the master startup loop
> where it waits for RS to heartbeat in. We had thought at the time that 92
> would have a different solution but it is still relying on heartbeats to
> learn about RSs.
> For now, we should definitely bring these config params into 92/trunk.
> Otherwise this is an incompatible regression and adding these will also make
> things like what was just reported over in HBASE-4603 trivial to fix in an
> optimal way.
--
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
