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 <https://issues.apache.org/jira/browse/STORM-2293> and STORM-2325 <https://issues.apache.org/jira/browse/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 <[email protected]>님이 작성: > 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: > > http://ip-161-12-410-48.eu-west-1.compute.internal:8000/dumps/<name of my > topology> > > Please note that the "Host" on the same line is > ip-161-12-410-48.eu-west-1.compute.internal, so I guess that's the root of > my issue ; I guess it should rather be a public FQDN like > ec2-12-132-11-1.eu-west-1.compute.amazonaws.com > > Any idea how to make Storm / Nimbus / Nimbus UI use public FQDNs instead > of private ones? > > Thanks, > Alexandre > > >
