[
https://issues.apache.org/jira/browse/STORM-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132313#comment-15132313
]
Jungtaek Lim commented on STORM-1492:
-------------------------------------
While I'm curious it's worth to make an effort, we could filter out some of
loopback addresses which are not same to NimbusInfo's host and port from
nimbus.seeds from function "nimbus-summary" in core.clj.
We just filter out only "localhost" if NimbusInfo's host and port is not
"localhost".
Nevertheless, we'd better to document that it's encouraged to set nimbus.seeds
to hostname of the machine. Since it should be same to NimbusInfo's host and
port to avoid this odd behavior, it would be much better to set
"storm.local.hostname" to same address, too.
> With nimbus.seeds set to default, a nimbus for localhost may appear "Offline"
> -----------------------------------------------------------------------------
>
> Key: STORM-1492
> URL: https://issues.apache.org/jira/browse/STORM-1492
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 1.0.0
> Reporter: P. Taylor Goetz
> Assignee: Jungtaek Lim
> Priority: Minor
>
> With the default value for {{nimbus.seeds}} ({{["localhost"]}}) Storm UI may
> list one "Offline" nimbus for localhost, and another as "Leader" for the
> resolved machine name.
> Steps to reproduce (assumes ZK is running; all on local machine):
> 1. Clean install of 1.0.0-SNAPSHOT (do not modify {{storm.yaml}})
> 2. Start nimbus
> 3. Start supervisor
> 4. Start ui
> 5. Navigate to http://localhost:8080
> A workaround is to modify {{storm.yaml}} and replace "localhost" with the
> hostname of the machine in {{nimbus.seeds}}.
> While trivial to correct, this may confuse users. One approach is to simply
> document this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
