[
https://issues.apache.org/jira/browse/STORM-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303617#comment-14303617
]
ASF GitHub Bot commented on STORM-534:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/394#issuecomment-72693203
Sorry this took me so long to respond to. I am kind of swamped :). I do
like the idea of being able to access the version numbers for nimbus, but also
for the supervisors. This becomes especially important for HA and rolling
upgrades of large clusters. It is good to be able to verify that all of the
nodes are on the versions you expect them to be on. I am OK with it being
stored in ZK, so long as it is not written/read very frequently.
Also if you think the configuration takes up too much room please take a
look at https://github.com/apache/storm/pull/328 which makes the config
paginated.
> Store Nimbus Server Information in zookeeper path
> {storm.zookeeper.root}/nimbus
> -------------------------------------------------------------------------------
>
> Key: STORM-534
> URL: https://issues.apache.org/jira/browse/STORM-534
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 0.10.0
> Reporter: caofangkun
> Assignee: caofangkun
> Priority: Minor
>
> 1) {nimbus.host} {nimbus.thrift.port} {storm.version} will be stored in
> {storm.zookeeper.root}/nimbus like "localhost:8826:0.9.3-r1234"
> 2) Storm Clients only need to configure {storm.zookeeper.root} to get Nimbus
> Server Information, Configuration like {nimbus.host} {nimbus.thrift.port}
> {storm.version} will be ignored
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
