[ https://issues.apache.org/jira/browse/HBASE-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499219#comment-13499219 ]
Gregory Chanan commented on HBASE-7170: --------------------------------------- I traced its history, it was in the initial commit of HConnectionManager: https://github.com/apache/hbase/commit/07657c40e9528b32bb17f2af72f3b3c34eeada7f so no additional information on why it was there in the first place. > [0.94 branch] Allow HConnectionImplementation to reconnect to master multiple > times > ----------------------------------------------------------------------------------- > > Key: HBASE-7170 > URL: https://issues.apache.org/jira/browse/HBASE-7170 > Project: HBase > Issue Type: Task > Reporter: Gregory Chanan > Assignee: Gregory Chanan > Priority: Minor > Fix For: 0.94.4 > > Attachments: HBASE-7170.patch > > > HBASE-5058 retained the old behavior of managed HConnections not retrying > their connection to master b/c of the "masterChecked" variable. > This behavior isn't great though, because you can get in the following > situation: > 1) Connect to master using HBaseAdmin > 2) Master goes down > 3) New master takes over > 4) The HBaseAdmin object is now useless > The client needs to create a new HBaseAdmin in this case. -- 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