[
https://issues.apache.org/jira/browse/ACCUMULO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806438#comment-13806438
]
Josh Elser commented on ACCUMULO-1286:
--------------------------------------
bq. What is the use-case for getting the fail-over master locations from this
API call?
I think there are multiple health/status use cases that could be addressed by
knowing the master servers that exist. Running Accumulo on yarn (HOYA) also has
some application of wanting to know this kind of information for system
"introspection".
I think the addition of a new method would be a good start. Whether or not we
deprecate the getMasterLocations and make a better named method isn't a huge
deal to me. Normal clients never use this method anyways, so it's not of much
consequence IMO.
> getMasterLocations never returns more than one master
> -----------------------------------------------------
>
> Key: ACCUMULO-1286
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1286
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.3, 1.5.0, 1.6.0
> Reporter: Eric Newton
> Priority: Minor
> Fix For: 1.7.0
>
>
> ZooKeeperInstance always returns an empty list, or whoever has the zookeeper
> lock.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
