As discussed/decided by the TLC, a final patch needs to be derived by
converging upon the good and working ideas from the patches shared by Hans and
Mahesh.
The final patch also needs thorough testing. Moving this to 4.5 as a part of
preparation of 4.4 RC1.
---
** [tickets:#654] MDS improvements**
**Status:** review
**Created:** Wed Dec 11, 2013 10:26 AM UTC by Hans Feldt
**Last Updated:** Wed Jan 29, 2014 11:40 AM UTC
**Owner:** A V Mahesh (AVM)
Identified short comings:
- MDS does not use the segmentation/reassembly support in the underlying
transport protocol. For example TIPC accepts messages upto 66000 bytes
- The built in segmentation/reassembly is totally insecure, lost fragments are
not retransmitted and the complete message is dropped (without users knowledge)
- In TIPC mode DEST_DROPPABLE is not used at all. This means that messages can
be silently dropped at a receiving node at congestion.
Suggested improvements:
1) Introduce a variable fragmentation limit when sending messages. This needs
to be based on information received at service discovery. If the sender is
"old" use the classic 1400 byte limit. If the sender is new, first use TIPCs
segmentation/reassembly and then the MDS one.
2) Configure DEST_DROPPABLE=False and use returned messages for diagnostics (as
a first step). That means only for logging purposes and not for retransmission
(which is not possible since messages are not stored in a send queue)
I have working prototype patches for both. Will send out them shortly.
Using TIPC segmentation/reassembly gives a number of advantages:
- reduced risk of link congestion on sending node since TIPC counts messages
not bytes
- secure transport of large messages, TIPC handles retransmission
- possibly improved characteristics due to implicit use of Ethernet jumbo frames
Long term we should consider if MDS segmentation/reassembly can be removed.
Sending large messages should really be using stream sockets.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
