[
https://issues.apache.org/jira/browse/KNOX-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417345#comment-16417345
]
ASF subversion and git services commented on KNOX-1228:
-------------------------------------------------------
Commit 98dbfe990887c2ce032015781cc99d4ae8198cbe in knox's branch
refs/heads/master from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=98dbfe9 ]
KNOX-1228 - Atlas HA ZooKeeper Config Discovery
> Atlas HA ZooKeeper Config Discovery
> -----------------------------------
>
> Key: KNOX-1228
> URL: https://issues.apache.org/jira/browse/KNOX-1228
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.1.0
> Reporter: Phil Zampino
> Assignee: Phil Zampino
> Priority: Major
> Fix For: 1.1.0
>
>
> Now that Atlas HA is supported via a custom dispatch that relies on
> ZooKeeper, Knox can support dynamic discovery of the corresponding ZooKeeper
> details, which it can automatically populate in the ATLAS and ATLAS-API
> service declarations in generated topologies for which the HaProvider is
> configured.
> Since Atlas configuration has two distinct properties for specifying the
> ZooKeeper ensemble, support for specifying multiple ensemble properties in
> order of precedence in the configuration must be added.
> Example:
> {code}
> # ATLAS
> ATLAS.config=ATLAS:application-properties
> ATLAS.enabled=atlas.server.ha.enabled
> ATLAS.ensemble=atlas.server.ha.zookeeper.connect,atlas.kafka.zookeeper.connect
> ATLAS.namespace=atlas.server.ha.zookeeper.zkroot
> {code}
> For Atlas, the atlas.server.ha.zookeeper.connect property must be checked as
> an override before falling back to the value of the
> connect,atlas.kafka.zookeeper.connect property.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
