[DISPATCH-523] Topology changes can cause in-flight deliveries to be stuck in the ingress router

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.6.1
• Fix Version/s: 0.7.0
• Component/s: Router Node
• Assignee: Ted Ross
• Reporter: Ted Ross
• Created: 23/Sep/16 20:44
• Updated: 04/Dec/18 13:31
• Resolved: 23/Sep/16 21:13

Description

Scenario:

• A network where messages are being delivered from the ingress router, across a neighbor router to a third router where the destination is attached.
• The neighbor router is shut down.
• There is a valid alternative path to the destination.
• A message delivery arrives immediately after the neighbor router is lost (before the route engine can compute the new path).

In the above scenario, the delivery may wind up on the ingress link's "undelivered" list and stay there indefinitely, even after the network has been completely restored.