[infinispan-issues] [JBoss JIRA] (ISPN-3843) Remove broadcast/unicast optimization in JGroupsTransport

[Dan Berindei (JIRA)]

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

Dan Berindei commented on ISPN-3843:
------------------------------------

It's probably not that important, as messages from different senders are not ordered anyway (either by UNICAST3 or NAKACK2). In asynchronous non-tx caches updates for the same key are ordered because they are all sent from the primary owner, but the primary owner will also change for at least some of the keys when the cluster size changes.

> Remove broadcast/unicast optimization in JGroupsTransport
> ---------------------------------------------------------
>
>                 Key: ISPN-3843
>                 URL: https://issues.jboss.org/browse/ISPN-3843
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 6.0.0.Final
>            Reporter: Dan Berindei
>             Fix For: 7.1.0.CR1
>
>
> The broadcast/unicast optimization in JGroupsTransport can break the message ordering for regular messages, because NAKACK[2] and UNICAST[2|3] have their own ordering.
> We should test if this optimization really brings any performance benefits and eliminate it, at least for asynchronous commands.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)