storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From howard chen <>
Subject Why my local storm need to call the remote zookeepers if I am deploying a jar to nimbus?
Date Sun, 02 Feb 2014 16:20:25 GMT
When I call my nimbus to submit a jar from public thru a firewall with
port 6627, I assume that this is the only requirement I need to meet,
right? I assume I don't need to contact the zookeepers, supervisors
behind the firewall directly, as the nimbus will invoke them on behalf
of myself, right?

However, I get the error when I submit a jar from my local machine to
remote (firewall protected with only port 6627 opened), e.g.

4340 [main] INFO - Starting
4512 [main-EventThread] INFO backtype.storm.zookeeper - Zookeeper
state update: :connected:none 4542 [main] INFO - Starting
4551 [main-SendThread(localhost:2000)] WARN
org.apache.zookeeper.ClientCnxn - Session 0x0 for server null,
unexpected error, closing socket connection and attempting reconnect No route to host at Method) ~[na:1.7.0_40] at ~[na:1.7.0_40] at ~[na:1.7.0_40] at
~[na:1.7.0_40] at
~[zookeeper-3.3.3.jar:3.3.3-1073969] at

I don't have this error when I am deploying inside the private
network, any idea?

View raw message