[tickets] [opensaf:tickets] #2609 dtm: Handle unicast sender congestion
- **Milestone**: 5.19.01 --> future --- ** [tickets:#2609] dtm: Handle unicast sender congestion** **Status:** unassigned **Milestone:** future **Created:** Wed Oct 04, 2017 11:44 AM UTC by Anders Widell **Last Updated:** Wed Jan 09, 2019 09:23 PM UTC **Owner:** nobody When using unicast instead of broadcast or multicast, we have the possibility to get congestion when sending the unicast messages to all peer nodes, resulting in success for some nodes and failure for other nodes. We should keep track of which nodes that have failed, and use e.g. EPOLLOUT to get notified when sending is possible again. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2609 dtm: Handle unicast sender congestion
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2609] dtm: Handle unicast sender congestion** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Wed Oct 04, 2017 11:44 AM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody When using unicast instead of broadcast or multicast, we have the possibility to get congestion when sending the unicast messages to all peer nodes, resulting in success for some nodes and failure for other nodes. We should keep track of which nodes that have failed, and use e.g. EPOLLOUT to get notified when sending is possible again. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2609 dtm: Handle unicast sender congestion
--- ** [tickets:#2609] dtm: Handle unicast sender congestion** **Status:** unassigned **Milestone:** 5.17.10 **Created:** Wed Oct 04, 2017 11:44 AM UTC by Anders Widell **Last Updated:** Wed Oct 04, 2017 11:44 AM UTC **Owner:** nobody When using unicast instead of broadcast or multicast, we have the possibility to get congestion when sending the unicast messages to all peer nodes, resulting in success for some nodes and failure for other nodes. We should keep track of which nodes that have failed, and use e.g. EPOLLOUT to get notified when sending is possible again. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
