Hi,
I'm trying to fine tune my PUB-SUB system. I've set the high water mark
(RCVHWM/SNDHWM) to zero (no-limit) and now I would like to see how high the
"water" actually gets after running the system for a while.
Using zmq_getsockopt() with ZMQ_RCVHWM/ZMQ_SNDHWM only retrieves the high water
?Thanks. That's a good workaround. I can send the signal from the signal
handler. -Martin
From: zeromq-dev on behalf of Doron
Somech
Sent: Wednesday, January 16, 2019 03:14
To: ZeroMQ development list
Subject: Re: [zeromq-dev] pyzmq poller and EINTR
The C library provides zmq_poll(), which returns -1 on error and set the errno
accordingly. I'm particularly interested by errno=EINTR, which means: "The
operation was interrupted by delivery of a signal before any events were
available."
Now if we look at the Python code there is
Hi,
Let's say I've made several subscriptions using zmq_setsockopt(sock,
ZMQ_SUBSCRIBE, ...) and later I want to remove all these subscriptions.
I know I can remove each subscription by successively invoking
zmq_setsockopt(sock, ZMQ_UNSUBSCRIBE, ...), but I was just wondering if there
was a
Hi,
I'm experimenting with zmq_socket_monitor(). I have a XSUB socket that I'm
monitoring. The monitoring works fine. I'm just trying to understand how I can
enable/disable monitoring back-and-forth by calling zmq_socket_monitor().
I tried to enable/disable/re-enable monitoring by invoking
I want to be able to turn on/off monitoring using zmq_socket_monitor().
I turn on monitoring as follows:
zmq_socket_monitor(sock_to_monitor_p, "inproc://monitor-my-sock",
ZMQ_EVENT_ALL)
And I turn it off this way:
zmq_socket_monitor(sock_to_monitor_p, NULL, 0)
I designed my main process to
I'm designing a multi-node pub-sub pattern (each node is a separate computer
running Debian Linux). The number of nodes is configurable and can change over
time (i.e. through configuration I can add or remove nodes). I want to use
XPUB-XSUB proxies on each node as depicted below. The following
