Topology dies immediately upon deployment when configured with two workers instead of one

2014-01-30 Thread Mark Greene
Exception in log: 2014-01-31 02:58:14 task [INFO] Emitting: change-spout default [[B@38fc659c] 2014-01-31 02:58:14 task [INFO] Emitting: change-spout __ack_init [1863657906985036001 0 2] 2014-01-31 02:58:14 util [ERROR] Async loop died! java.lang.RuntimeException: org.zeromq.ZMQException: Invalid

Re: Topology dies immediately upon deployment when configured with two workers instead of one

2014-01-30 Thread bijoy deb
Hi Mark, Storm uses the internal queuing (through ZMQ) only when there is a communication between two worker processes is required,which is why this error comes up only when you set num_workers>1. Though I won't be able to help with with an exact solution for this,I can provide some pointers: a)

Re: Topology dies immediately upon deployment when configured with two workers instead of one

2014-01-31 Thread Mark Greene
> > Storm uses the internal queuing (through ZMQ) only when there is a > communication between two worker processes is required,which is why this > error comes up only when you set num_workers>1. I'm a little confused by the answer, are you suggesting that storm cannot run more than one worker ev

Re: Topology dies immediately upon deployment when configured with two workers instead of one

2014-01-31 Thread Nathan Leung
It can work with ZMQ, but you MUST use the version specified (2.1.7). Newer versions change the API which causes errors, which might be what you are seeing. Is the version of libzmq you installed the same as the one you are using in production? On Fri, Jan 31, 2014 at 9:47 AM, Mark Greene wrot

Re: Topology dies immediately upon deployment when configured with two workers instead of one

2014-01-31 Thread Mark Greene
We are on 2.1.7 on all environments, they are all managed by chef. On Fri, Jan 31, 2014 at 9:51 AM, Nathan Leung wrote: > It can work with ZMQ, but you MUST use the version specified (2.1.7). > Newer versions change the API which causes errors, which might be what you > are seeing. Is the ver

Re: Topology dies immediately upon deployment when configured with two workers instead of one

2014-01-31 Thread Nathan Leung
Are you also using the forked version of jzmq? On Fri, Jan 31, 2014 at 11:26 AM, Mark Greene wrote: > We are on 2.1.7 on all environments, they are all managed by chef. > > > On Fri, Jan 31, 2014 at 9:51 AM, Nathan Leung wrote: > >> It can work with ZMQ, but you MUST use the version specified

Re: Topology dies immediately upon deployment when configured with two workers instead of one

2014-01-31 Thread bijoy deb
Hi Mark, Ideally it should work once you use the correct (older) version of ZMQ.But since you say you are getting the error with 2.1.7 version,I would suggest you to try the below steps and let me know if that worked: 1) Build the jzmq using steps mentioned in below site: https://github.com/natha