accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1286) getMasterLocations never returns more than one master
Date Sun, 27 Oct 2013 19:18:30 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806428#comment-13806428
] 

Christopher Tubbs commented on ACCUMULO-1286:
---------------------------------------------

I was under the impression that this method existed before queued fail-over masters existed,
in order to support multiple active masters, if that ever were to become a thing.

In any case, active masters is certainly that is the current semantics. So, rather addressing
it as a bug, we should probably discuss the merits of changing the semantics (vs. adding an
additional mechanism to view the fail-over masters). What is the use-case for getting the
fail-over master locations from this API call? Can that use case be satisfied with another
method called, "getBackupMasterLocations" or similar without changing current semantics? If
so, are there reasons we'd prefer not to choose that option?

> 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)

Mime
View raw message