[zeromq-dev] C Based ZeroMQ Aggregation Server Problems...

[Henry Geddes]

So just to update you on progress with this.  We have upgraded all boxes to now run 2.1.10 and cleaned up some of the code to remove anything that would not compile with the new version.  We are currently running the sink to see if the problem arises over night.  I am also trying to familiarize myself with the inner workings of zmq.  We did try rolling back the version to the previous zmq version for the sink but that did not appear to keep up with the traffic.  We also are trying to identify if it is a client connecting into the sink that may be having an effect.

Hopefully it will remain stable through the night.

-----Original Message-----
From: zeromq-dev-bounces at lists.zeromq.org [mailto:zeromq-dev-bounces at lists.zeromq.org] On Behalf Of Henry Geddes
Sent: Monday, October 17, 2011 5:34 PM
To: ZeroMQ development list
Subject: Re: [zeromq-dev] C Based ZeroMQ Aggregation Server Problems...

We saw the recv in strace.  It is the system call.  

I am adding all info we have into the bug right now.  We will try the upgrading of all programs to 2.1.8 tomorrow and make sure all versions are the same.  Not sure what to add as a test case right now as we cannot force a reproduce on this.

We will loop back around tomorrow.

-----Original Message-----
From: zeromq-dev-bounces at lists.zeromq.org [mailto:zeromq-dev-bounces at lists.zeromq.org] On Behalf Of Pieter Hintjens
Sent: Monday, October 17, 2011 5:09 PM
To: ZeroMQ development list
Subject: Re: [zeromq-dev] C Based ZeroMQ Aggregation Server Problems...

On Mon, Oct 17, 2011 at 6:45 PM, Henry Geddes <hgeddes at zynga.com> wrote:

> Are there any known issues when passing messages between 2.1.4 and 2.1.8?  We are just wondering if it may be an incompatibility between versions?

All 2.x versions are compatible, in theory. But indeed this might be
due to a malformed message landing and confusing things. In that case
it should be easy to reproduce.

Ideally we can get this to a reproducible state with a minimal test case.

Did you attach a debugger to the blocked process to see where it's
waiting? There isn't a recvfrom call anywhere in the codebase afaics.

-Pieter
_______________________________________________
zeromq-dev mailing list
zeromq-dev at lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
zeromq-dev at lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev