[infinispan-issues] [JBoss JIRA] (ISPN-4503) Commands with topology id 0 are not properly ignored on joiners

RH Bugzilla Integration (JIRA) issues at jboss.org
Thu May 14 18:50:21 EDT 2015


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

RH Bugzilla Integration commented on ISPN-4503:
-----------------------------------------------

Sebastian Łaskawiec <slaskawi at redhat.com> changed the Status of [bug 1220328|https://bugzilla.redhat.com/show_bug.cgi?id=1220328] from MODIFIED to ON_QA

> Commands with topology id 0 are not properly ignored on joiners
> ---------------------------------------------------------------
>
>                 Key: ISPN-4503
>                 URL: https://issues.jboss.org/browse/ISPN-4503
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core, State Transfer
>    Affects Versions: 7.0.0.Alpha4
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>              Labels: testsuite_stability
>             Fix For: 7.0.0.Beta1
>
>
> InboundInvocationHandlerImpl is supposed to ignore commands sent with a topology id smaller than the first topology id in which the local node was a member. But there is a loophole when the command was sent with topology id 0.
> This is visible in StateTransferFunctionalTest, where the writing thread keeps the cpu busy and can delay the 2nd node joining for a long time (especially when run on a single core with {{taskset -c 0}}). For some reason, the PrepareCommands are sent only to the local node, while the TxCompletionNotificationCommands are sent to the entire cluster ({{null}}). When the 2nd node manages to join, it receives a lot of TxCompletionNotificationCommands and processing them delays the processing of the rebalance commands. Since the writes eventually block waiting for the new topology to be installed on the joiner, the delayed rebalance commands cause the write to time out.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)



More information about the infinispan-issues mailing list