[
https://issues.jboss.org/browse/JGRP-2172?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on JGRP-2172:
-----------------------------------
I would prefer fair ordering to preferring threads vs messages.
The queue could accept two things: either messages or thread tokens. When the {{NB_FC}} is
not set and there's not enough credits, the thread adds a token to the queue, waiting
for it to be released from the queue. When the credits arrive, messages and tokens would
be served FIFO because of the queue.
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)