You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Daniel Schonfeld (JIRA)" <ji...@apache.org> on 2014/10/07 05:01:33 UTC

[jira] [Created] (STORM-520) Using storm.local.hostname causes bolts to not communicate with each other

Daniel Schonfeld created STORM-520:
--------------------------------------

             Summary: Using storm.local.hostname causes bolts to not communicate with each other
                 Key: STORM-520
                 URL: https://issues.apache.org/jira/browse/STORM-520
             Project: Apache Storm
          Issue Type: Bug
    Affects Versions: 0.9.2-incubating
         Environment: Docker container (Docker > 1.1.2)
            Reporter: Daniel Schonfeld


In our setup we run different supervisors as docker container on top of CoreOS.

If I use docker's -h (host) and give the container the same hostname as the host machine, the bolts are able to register with nimbus correctly, talk to each other as well as transfer data inside the same container between different workers located on the same machine.

Utilizing 'storm.local.hostname' instead of using docker's -h option results in the bolts having a hard time (read: unable to) communicating between workers on the same machine/container (we only run one container per physical machine which contains 4 workers + supervisor) and having sporadic success (50/50) communicating with bolts in different machines.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)