storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jungtaek Lim <>
Subject Re: How to correctly setup Nimbus UI to have public instead of private FQDN for debug
Date Wed, 25 Jan 2017 09:43:14 GMT
You can set public FQDN via 'storm.local.hostname' to config file (normally
storm.yaml) on each node.
Without this configuration, Storm processes will refer local hostname which
is described from /etc/hosts.

After setting up 'storm.local.hostname' you might encounter STORM-2293
<> and STORM-2325
<>. They will be resolved
and included to the next release. If you don't think they're critical, you
can set it up now and give it a try.

- Jungtaek Lim (HeartSaVioR)

2017년 1월 23일 (월) 오전 6:32, Alexandre Vermeerbergen <>님이

> Hello,
> I deployed our application to an Apache Storm cluster (currently version
> 1.0.1) on Amazon E2C instances.
> Nimbus UI works like a charm, except for the "debug" links which URLs are
> based on private FQDN instead of public FDQN address of VMs.
> For example, when clicking on the debug link of one of the executors, I
> have a URL looking like this one, which isn't accessible from outside the
> VM:
><name of my
> topology>
> Please note that the "Host" on the same line is
>, so I guess that's the root of
> my issue ; I guess it should rather be a public FQDN like
> Any idea how to make Storm / Nimbus / Nimbus UI use public FQDNs instead
> of private ones?
> Thanks,
> Alexandre

View raw message