Opened 7 years ago

Closed 5 years ago

#1350 closed enhancement (wontfix)

Use Delivery Status Message routing as a hint for client message path selection

Reported by: zzz Owned by:
Priority: minor Milestone: 0.9.18
Component: router/general Version:
Keywords: Cc:
Parent Tickets: Sensitive: no


Idea from orignal:

Currently in InboundMessageDistributor? (IMD) we pick a random OB tunnel to return the DeliveryStatusMessage? (DSM) garlic to the originator's lease. We don't pick closest-pair and we don't cache the choice. Nor do we communicate those decisions to OutboundClientMessageOneShotJob? (OCMOSJ) where we make similar path selection decisions for outbound client messages.

While the returned garlic could be going anywhere, in practice it's going to a lease in the same LS as the client messages. Orignal suggests we should use that lease as a strong hint that the far-end considers that lease to be "good" and to use it in the path for client messages. Not sure how much the Java router knows about what tunnes of his are "good" though…

In addition, using XOR OBEP/IBGW pair selection in IMD and/or using the cached pair from OCMOSJ could help reduce OBEP/IBGW connection congestion network-wide and reduce latencies.

Right now we send (and process) the DSM clove before the data clove so it would be IMD driving OCMOSJ the first time. But OCMOSJ has the cache so it would tell IMD what to do next time.

For further research and analysis…


Change History (3)

comment:1 Changed 7 years ago by zzz

Basic XOR-closeness for DSM tunnel pair selection in feb51c6384a26593479acc74cf0709db1a1b1503, for a little reduction in network-wide OBEP/IBGW connections.

Not clear if there's an easy way to do the main idea. You don't know what leaseset things are coming from. Tough to link up those two parts of the code too.

comment:2 Changed 5 years ago by str4d

Status: newopen

comment:3 Changed 5 years ago by zzz

Resolution: wontfix
Status: openclosed
Note: See TracTickets for help on using tickets.