[DISPATCH-58] Router/Broker interaction - Unroutable/released messages are continually resent

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.2
• Fix Version/s: 0.6.0
• Component/s: Routing Engine
• Assignee: Ken Giusti
• Reporter: Ted Ross
• Created: 27/May/14 13:42
• Updated: 20/Nov/17 18:39
• Resolved: 10/May/16 17:57

Description

There's an issue with the fact that the router releases unroutable messages. When the message originates from a broker, that broker will continually re-send the message, burning network bandwidth, until the message becomes routable.

Here are a few ideas as to how to address this situation:

• Have the ingress router hold the message for a time if it is not routable to avoid rapidly releasing.
• Introduce a notion of not-routable-now vs. not-routable-ever. This would allow the router to hold-for-retry or immediately reject.

Are there cases where the current behavior is desirable? If the producer node has multiple outgoing links, a quick release would allow it to use an alternate link.