[ https://issues.apache.org/jira/browse/HBASE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696719#comment-13696719 ]
Hudson commented on HBASE-4360: ------------------------------- Integrated in HBase-TRUNK #4203 (See [https://builds.apache.org/job/HBase-TRUNK/4203/]) HBASE-4360 Maintain information on the time a RS went dead (samar) (Revision 1498274) Result = FAILURE nkeywal : Files : * /hbase/trunk/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/master/MasterStatusTmpl.jamon * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/DeadServer.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestDeadServer.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterStatusServlet.java > Maintain information on the time a RS went dead > ----------------------------------------------- > > Key: HBASE-4360 > URL: https://issues.apache.org/jira/browse/HBASE-4360 > Project: HBase > Issue Type: Improvement > Components: master > Affects Versions: 0.94.0 > Reporter: Harsh J > Assignee: samar > Priority: Minor > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-4360_1.patch, HBASE-4360_2.patch, > HBASE-4360_3.patch, HBASE-4360_4.patch, master-status1.png > > > Just something that'd be generally helpful, is to maintain DeadServer info > with the last timestamp when it was determined as dead. > Makes it easier to hunt the logs, and I don't think its much too expensive to > maintain (one additional update per dead determination). -- 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