[
https://issues.apache.org/jira/browse/HBASE-20109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384587#comment-16384587
]
Hudson commented on HBASE-20109:
--------------------------------
Results for branch branch-1, done in 2 hr 11 min and counting
[build #237 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/237/]:
----
details (if available):
(x) *{color:red}-1 overall{color}*
Committer, please check your recent inclusion of a patch for this issue.
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
> Add Admin#getMaster API to branch-1
> -----------------------------------
>
> Key: HBASE-20109
> URL: https://issues.apache.org/jira/browse/HBASE-20109
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Affects Versions: 1.4.2
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 1.5.0
>
> Attachments: HBASE-20109-branch-1.patch, HBASE-20109-branch-1.patch
>
>
> Right now the only public API available in branch-1 to the client to learn
> the server name of the active master is Admin#getClusterStatus#getMaster,
> returning ServerName. On a cluster of any size getClusterStatus is expensive,
> especially if used only to retrieve the active master name.
> Later versions have
> {code}
> ServerName Admin#getMaster()
> {code}
> for lightweight discovery of the active master location. Add this to branch-1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
