[DISPATCH-1532] Reimplement mobile-sync as a core module

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.11.0
• Component/s: Routing Engine
• Assignee: Ted Ross
• Reporter: Ted Ross
• Created: 18/Dec/19 20:07
• Updated: 10/Aug/20 13:24
• Resolved: 14/Jan/20 21:58

Description

The code in Qpid Dispatch Router currently does mobile address synchronization between routers in the Python router module.  This has a couple of drawbacks in cases where there are large numbers of addresses:

• The address strings are stored twice:  once in the main address lookup hash table and again in the Python mobile address module.
• Address lookup on the Python side is inefficient and has been a bottleneck (improved recently by a patch from Gordon Sim).
• Python processing is single threaded.  A large mobile address update can cause delays in processing management requests and link-state topology maintenance.

The python router module was intended to be an on-the-side control-plane module that was not in the critical path for any performance-related activities.  With large numbers of addresses in a network, synchronizing address locations becomes performance-related.

To address these issues, mobile address synchronization can be moved into a core module where it can use and share the same address table that is used by the router core for making high speed routing decisions.  In the process, it will leave the python modules alone to process management requests and topology maintenance uninterrupted.

Issue Links

• fixes: DISPATCH-1502 large scale link disconnects can push memory up
• relates to: DISPATCH-1459 Python3: exception thrown when processing MAUs
• links to: GitHub Pull Request #654