[
https://issues.jboss.org/browse/JGRP-1733?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1733:
--------------------------------
The main advantage is that messages flagged as {{OOB | DONT_BUNDLE}} or {{OOB | INTERNAL |
DONT_BUNDLE}} don't end up getting in a batch, possibly even by a regular thread.
These types of messages are often used internally, and cannot get stuck behind other
(application) messages in a batch, which delay deliver of the internal message or even
block (e.g. RPCs waiting for a response).
UNICAST / NAKACK: OOB messages should be marked as OOB_DELIVERED
before adding them to the table
------------------------------------------------------------------------------------------------
Key: JGRP-1733
URL:
https://issues.jboss.org/browse/JGRP-1733
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.5
Currently, OOB messages are added to the table, then passed up unless they're already
marked as OOB_DELIVERED. This could happen if another thread removed messages from the
table and passed them up before the current thread could pass the message up.
However, this work stealing might be detrimental: if the stealing thread batched messages
up and 'stole' OOB messages (and those messages blocked), then the rest of the
batch would be blocked from delivery.
This is the same though if a batch only contains regular messages...
However, this would make things simpler as threads from the regular pool would never
deliver OOB messages (but not the other way round, OOB thread could still deliver regular
messages).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira