[
https://issues.apache.org/jira/browse/HBASE-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172061#comment-13172061
]
Lars Hofhansl commented on HBASE-5058:
--------------------------------------
Actually it is the other way round... :)
masterChecked is set to true to avoid trying to retrieve the master in the
future. This is fine for the managed HConnection as it will just be removed and
another is created when needed.
For an HConnection that is passed from the outside, it has to be possible to
try again. So if the HConnection is managed we retain the old behavior (i.e.
only try once, give up after that, even if that failed).
For an unmanaged connection we try again unless we actually found a master. So
masterChecked is set to true if either the connection is managed (always avoid
retrying), or we found a master.
> Allow HBaseAmin to use an existing connection
> ---------------------------------------------
>
> Key: HBASE-5058
> URL: https://issues.apache.org/jira/browse/HBASE-5058
> Project: HBase
> Issue Type: Sub-task
> Components: client
> Affects Versions: 0.94.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Minor
> Fix For: 0.94.0
>
> Attachments: 5058-v2.txt, 5058.txt
>
>
> What HBASE-4805 does for HTables, this should do for HBaseAdmin.
> Along with this the shared error handling and retrying between HBaseAdmin and
> HConnectionManager can also be improved. I'll attach a first pass patch soon.
--
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
