I have seen this when I make a mistake and over-consume from the publisher on multipart messages. the subscriber then blocks. In my case the next message eventually comes along and things resume, but out of sync.
To avoid this I created a small class that recvies the entire multipart message then it either has or has not enough "frames." I separated my interpretation of the frames from their recv. On Fri, Mar 11, 2016 at 6:39 AM, Navneet Kumar <[email protected]> wrote: > Hello everone > > I am building a pubsub, wherein the PUB and the SUB socket are on the same > host. > I am able to send lots of messages through it. The latency of the system > is around 2-50 ms. > > But out of blue some messages get stuck for 5-6 seconds before receiving. > I have put the logs and added timestamps to the message itself. > The publisher publishes and sets the time stamp, the subscriber timestamp > has a > difference of 5-10 seconds. This occurs for roughly 1 in 1000 messages. > > I am using aws c4.xlarge machine. I tried ss and there were few blips in > the recv and send queue. > If i am sending lots of messages in bulk then it sometimes get stuck and > the resumes, with no > messages being lost. Sometimes a single message itself without any other > load gets stuck. > > Has anyone faced such a scenario or give any pointers to look. > > > > -- > Navneet Kumar > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
