[jboss-jira] [JBoss JIRA] (JGRP-1732) UNICAST/NAKACK: threads from the internal thread pool should not do work stealing

Bela Ban (JIRA) jira-events at lists.jboss.org
Mon Nov 11 08:58:05 EST 2013


    [ https://issues.jboss.org/browse/JGRP-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922345#comment-12922345 ] 

Bela Ban commented on JGRP-1732:
--------------------------------

Oops, failures (OOBTest). Perhaps this is 4 (reg) --> 6 (reg) --> 5 (oob) ? When 6 is received, it is added to the table but not delivered as 5 is missing. When 5 is received it is delivered, but 6 is not delivered...
                
> UNICAST/NAKACK: threads from the internal thread pool should not do work stealing
> ---------------------------------------------------------------------------------
>
>                 Key: JGRP-1732
>                 URL: https://issues.jboss.org/browse/JGRP-1732
>             Project: JGroups
>          Issue Type: Enhancement
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.5
>
>
> In NAKACK\{2\} and UNICAST\{2,3\}, threads from all thread pools (regular, OOB and internal) add messages to the table, then grab as many (ordered) messages as possible from the table and pass them up.
> This could lead to the case where an internal thread passes up regular or OOB messages, which might block. There's a (small) chance that this exhausts the internal thread pool.
> Internal threads should therefore never block, and never steal work from other thread pools.
> SOLUTION:
> * An internal thread only adds the message to the table and passes it up if in order
> * If the internal message is OOB, it is passed up and then the thread returns

--
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


More information about the jboss-jira mailing list