[
https://issues.apache.org/jira/browse/STORM-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133180#comment-15133180
]
Jungtaek Lim commented on STORM-1492:
-------------------------------------
Since Nimbus HA setup is not mandatory, I expect many users will use default
setting, with not caring about the documentation.
So I agree that documenting is not enough.
But I also think we can't force users to set nimbus.seeds to FQDN of machine
for nimbus while they don't use Nimbus HA.
Maybe I'm wrong, but personally, I'm afraid that leaving the warning could be
also not enough. Many users don't even see nimbus log unless there're some
issues for cluster. If users don't start nimbus on their terminal session, they
don't even see the output of "storm nimbus" unless "storm nimbus" is not
functioning.
> 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)
