[zeromq-dev] [EXT] Re: Question about High Water and EPGM
Jamie Stewart
jamie at otcmarkets.com
Wed Jan 30 22:13:37 CET 2019
Hello,
I should clarify that we are using ZeroMQ version 4.1.1.
From: Jamie Stewart <jamie at otcmarkets.com>
Date: Wednesday, January 30, 2019 at 3:47 PM
To: ZeroMQ development list <zeromq-dev at lists.zeromq.org>
Cc: Matteo <matteo.brichese at gmail.com>
Subject: Re: [EXT] Re: [zeromq-dev] Question about High Water and EPGM
Thank you Matteo,
We are configuring the Pub/Sub EPGM send and receive sockets to hwm=0, send and receive buffers to 2621440. The host seems to have plenty of memory.
What is the expected behavior for a Pub/Sub pair with bursty sender, slow receiver, and both high-water marks set to 0? Should we see intermittent packet loss rather than the receiver abruptly stopping receiving from that sender?
If a high-water violation occurs, is there a way to learn about it through the ZeroMQ Java API? Is the only way for the receiver to resume receiving from the sender to close the socket and make a new one?
Sorry for so many questions, and thank you for your advice,
-Jamie Stewart
From: Matteo <matteo.brichese at gmail.com>
Date: Wednesday, January 30, 2019 at 3:41 PM
To: ZeroMQ development list <zeromq-dev at lists.zeromq.org>
Cc: Jamie Stewart <jamie at otcmarkets.com>
Subject: [EXT] Re: [zeromq-dev] Question about High Water and EPGM
I would check HWM on the sender too.
Also, it is possible you are running low on memory on the receiver?
On Wed, Jan 30, 2019 at 12:39 PM Jamie Stewart via zeromq-dev <zeromq-dev at lists.zeromq.org<mailto:zeromq-dev at lists.zeromq.org>> wrote:
Hello,
We use ZeroMQ with EPGM and pub/sub sockets in our Java applications. We are running into a problem with one app, a slow consumer, when it receives bursts of traffic. Sometimes during the burst, the slow consumer stops receiving data from the sender altogether. I had assumed that this behavior happens if I set a high-water mark on the receive socket, but that is set to 0.
Are there cases with EPGM where a bursty sender and a slow receiver could cause the receiver to stop receiving, even if the high-water mark for the receive socket is set to 0? If so, do you have tuning advice?
Thank you very much,
Jamie Stewart
________________________________
This e-mail (including any attachments) is confidential and may contain sensitive or legally privileged information. It is for the intended recipient only. Do not, directly or indirectly, copy, reproduce, print or disclose any part of this e-mail without the prior written consent of OTC Markets Group Inc. If you receive this message in error, please delete it and any attachments, and notify OTC Markets Group of misdelivery by return e-mail.
________________________________
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com<http://www.mimecast.com>
________________________________
_______________________________________________
zeromq-dev mailing list
zeromq-dev at lists.zeromq.org<mailto:zeromq-dev at lists.zeromq.org>
https://lists.zeromq.org/mailman/listinfo/zeromq-dev<https://lists.zeromq.org/mailman/listinfo/zeromq-dev>
--
Matteo
________________________________
This e-mail (including any attachments) is confidential and may contain sensitive or legally privileged information. It is for the intended recipient only. Do not, directly or indirectly, copy, reproduce, print or disclose any part of this e-mail without the prior written consent of OTC Markets Group Inc. If you receive this message in error, please delete it and any attachments, and notify OTC Markets Group of misdelivery by return e-mail.
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20190130/c96e3513/attachment.htm>
More information about the zeromq-dev
mailing list