[
https://issues.apache.org/jira/browse/STORM-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132480#comment-15132480
]
Robert Joseph Evans commented on STORM-1492:
--------------------------------------------
The real issue for me is that the default config uses localhost, so this shows
up for every cluster customers spin up with the default config. It does not
look good for storm. Documentation is great, but everyone will still see it.
I personally would prefer to see a slightly different approach.
nimbus.host is set to localhost in the default config.
if nimbus.host is set, but nimbus.seeds is not set nimbus.seeds will convert
nimbus.host to a FQDN and populate it to nimbus.seeds.
nimbus.seeds goes through all nimbus.seeds and validates that they are FQDNs
and will warn if they are not, because that is what actually causes the issue.
> 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)
