[zmq] Don't take a new port when restart server

Bug #1548836 reported by Oleksii Zamiatin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.messaging
Won't Fix
Undecided
Unassigned

Bug Description

Currently restarting the service we bind to a new random port each time, so already connected clients have no ability to reconnect to the service by means of KEEP_ALIVE connection.

Purpose: Zmq driver should not manage such kind of reconnects, it should be done by means of underlying ZeroMQ layers.

Possible solution:

When service starts and if it has server-id in the target <Target ... server="server1">:
 - check out this id in redis. (record presence in redis means repetitive runs, otherwise we run for the first time)
 - If the id presents, don't bind to a new random port but
   - get the port from redis record.
 - In case the port was not closed or it is hold by another process
  - bind to a random port as usual.

This solution would work if we don't have conflicting server names inside the same host.

Tags: zmq
tags: added: zmq
Andy Smith (ansmith-t)
Changed in oslo.messaging:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.