Databases
StackOverflow2013
Postsdbo
POHow should a ZeroMQ worker safely "hang up"?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow should a ZeroMQ worker safely "hang up"?
    primarykey
    data
    text
    <p>I started using ZeroMQ this week, and when using the Request-Response pattern I am not sure how to have a worker safely "hang up" and close his socket without possibly dropping a message and causing the customer who sent that message to never get a response. Imagine a worker written in Python who looks something like this:</p> <pre><code>import zmq c = zmq.Context() s = c.socket(zmq.REP) s.connect('tcp://127.0.0.1:9999') while i in range(8): s.recv() s.send('reply') s.close() </code></pre> <p>I have been doing experiments and have found that a customer at <code>127.0.0.1:9999</code> of socket type <code>zmq.REQ</code> who makes a fair-queued request just might have the misfortune of having the fair-queuing algorithm choose the above worker right after the worker has done its last <code>send()</code> but before it runs the following <code>close()</code> method. In that case, it seems that the request is received and buffered by the ØMQ stack in the worker process, and that the request is then lost when <code>close()</code> throws out everything associated with the socket.</p> <p>How can a worker detach "safely" — is there any way to signal "I don't want messages anymore", then (a) loop over any final messages that have arrived during transmission of the signal, (b) generate their replies, and then (c) execute <code>close()</code> with the guarantee that no messages are being thrown away?</p> <p><strong>Edit:</strong> I suppose the raw state that I would want to enter is a "half-closed" state, where no further requests could be received — and the sender would know that — but where the return path is still open so that I can check my incoming buffer for one last arrived message and respond to it if there is one sitting in the buffer.</p> <p><strong>Edit:</strong> In response to a good question, corrected the description to make the number of waiting messages plural, as there could be many connections waiting on replies.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBrandon Rhodes
    1. USBrandon Rhodes
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow should a ZeroMQ worker safely "hang up"?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow should a ZeroMQ worker safely "hang up"?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow should a ZeroMQ worker safely "hang up"?
      1. USZeissS
      1. VTFavorite
    1. COI found this thread, which is related-but-not-really: http://www.mail-archive.com/zeromq-dev@lists.zeromq.org/msg02338.html . Have you made any progress on this?
      singulars
      1. POHow should a ZeroMQ worker safely "hang up"?
      1. USJack Kelly
    2. CONo, I have not yet made further progress, and it appears that ZeroMQ expertise is a bit thinner on the ground than I had expected. Thanks for the link — it seems to involve message safety in the other direction, when a message is outbound, but brings up many of the same issues. Thanks!
      singulars
      1. POHow should a ZeroMQ worker safely "hang up"?
      1. USBrandon Rhodes
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload