[AMQ-4607] network connectors - new messageTTL and consumerTTL - split usage of networkTTL for mesh topology

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.8.0
• Fix Version/s: 5.9.0
• Component/s: Broker
• Labels: configuration configuration-addition mesh networkConnector networkTTL
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 27/Jun/13 11:57
• Updated: 18/Dec/13 17:11
• Resolved: 28/Jun/13 10:37

Description

currently networkTTL in a networkConnector (default=1) means that a message can go one hop and demand (or info about a consumer) can go one hop.
In a network (A<>B) messages and consumers can flow.

In a linear network (A<>B<>C) networkTTL needs to be 2 for messages and consumers to flow two hops from A to C.

In a mesh topology, (A<>B<>C<A>) a networkTTL=1 for consumers makes sense because there is at most one hop. However for messages, networkTTL > 1 is necessary if consumers need to hop around between brokers. Imagine a consumer on A which pulls messages to A from B, then the consumer moves to C, messages now need to hop again from A to C. This can repeat, essentially messageTTL(networkTTL) needs to be infinite.

With consumerTTL > 1 in a mesh, managing demand for proxy (demand) consumers and proxy proxy consumers becomes very difficult.

Issue Links

• is related to: AMQ-2327 Consumers left hanging in the large network of brokers
• relates to: AMQ-2180 infinite networkTTL
• relates to: AMQ-4465 Rethink replayWhenNoConsumers solution