[
https://issues.jboss.org/browse/JGRP-2172?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2172:
--------------------------------
[~rvansa] Good idea! Yes, I'm thinking UFC2/MFC2 makes sense, too. Using a queue makes
this more generic and once UFC2 / MFC2 has proven its stability in the field, we can
always deprecate UFC / MFC.
Thanks for the input,
Non-blocking flow control
-------------------------
Key: JGRP-2172
URL:
https://issues.jboss.org/browse/JGRP-2172
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.0.4
Sending a message through FlowControl (UFC, MFC) should not block if
{{Message.Flag.NB_FC}} (non-blocking flow control) is set.
Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else
unbounded). The max queue size is given in bytes, so we can estimate what the memory
penalty for reaching that size would be (if bounded).
The queued messages are sent when credits arrive. TBD: when credits arrive, should
blocked threads or queued messages be released first?
Non-blocking flow control can be used by both external and internal threads.
If the queue is unbounded, then it is the responsibility of the application (e.g.
Infinispan) to make sure the queue doesn't grow to an untenable size.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)