[ https://issues.apache.org/jira/browse/HBASE-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172917#comment-13172917 ]
Jonathan Hsieh commented on HBASE-5063: --------------------------------------- @Stack Here's what I got from a local run: {code} Running org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 506.988 sec Running org.apache.hadoop.hbase.mapreduce.TestTableMapReduce Running org.apache.hadoop.hbase.mapred.TestTableMapReduce Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 501.953 sec <<< FAILURE! Running org.apache.hadoop.hbase.io.hfile.TestHFileBlock Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 76.135 sec {code} mapreduce.TestTableMapReduce seems to be a hang. (grr... how do I get maven just to spit out all test output instead of waiting for the test to "finish") mapred.TestTableMapReduce seems to be a failed MR job. > RegionServers fail to report to backup HMaster after primary goes down. > ----------------------------------------------------------------------- > > Key: HBASE-5063 > URL: https://issues.apache.org/jira/browse/HBASE-5063 > Project: HBase > Issue Type: Bug > Affects Versions: 0.92.0 > Reporter: Jonathan Hsieh > Assignee: Jonathan Hsieh > Priority: Critical > Attachments: HBASE-5063.patch, hbase-5063.v2.0.92.patch, > hbase-5063.v2.trunk.patch > > > # Setup cluster with two HMasters > # Observe that HM1 is up and that all RS's are in the RegionServer list on > web page. > # Kill (not even -9) the active HMaster > # Wait for ZK to time out (default 3 minutes). > # Observe that HM2 is now active. Tables may show up but RegionServers never > report on web page. Existing connections are fine. New connections cannot > find regionservers. > Note: > * If we replace a new HM1 in the same place and kill HM2, the cluster > functions normally again after recovery. This sees to indicate that > regionservers are stuck trying to talk to the old HM1. -- 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