[
https://issues.apache.org/jira/browse/HBASE-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-5058:
---------------------------------
Attachment: 5058-v3.txt
Here's an attempt I can live with.
Notice how (1) the master null check is pulled into the synchronized block and
(2) master is now set to null before the start of the loop (3) sets
masterChecked to managed.
The effect is that the current behavior is not changed. I.e. for a managed
connection we try only once. Unmanaged connection get a chance to retry on
subsequent calls, and since master is set to null, this would work even when
the master has moved since the first attempt.
> 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-v3.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
