[infinispan-issues] [JBoss JIRA] (ISPN-7322) Improve triangle algorithm: ordering by segment

[Radim Vansa (JIRA)]

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

Radim Vansa commented on ISPN-7322:
-----------------------------------

[~belaban] I disagree. Since we actually want to order only writes to each key (without respect to the other keys), full source ordering is excessive - one hiccup (lost/discarded message) delays all subsequent messages (until the problem is handled).

About thread creation - do you mean that you deliver (to app) OOB messages received in one batch separately (one msg per thread)? Can we just switch this off and deliver the whole batch sequentially? The processing on backup should be non-blocking (not sure if there's something blocking left yet).

> Improve triangle algorithm: ordering by segment
> -----------------------------------------------
>
>                 Key: ISPN-7322
>                 URL: https://issues.jboss.org/browse/ISPN-7322
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Core
>            Reporter: Pedro Ruivo
>            Assignee: Pedro Ruivo
>
> Current triangle algorithm uses regular message (FIFO ordered) between the primary owner and backup owners of a key. While it ensures that the backup owners receives the stream of updates in the same order, it makes everything slower since it doesn't allow different keys to be handled in parallel.
> "Triangle unordered" solves this problem by sending OOB messages (not ordered) between the primary and backup. To keep the consistency, Infinispan introduces the TriangleOrderManager that orders the updates based on the segment of the key.
> While it is not as perfect as ordering per key, the segments are static; this removes the complexity and avoids handling the cluster topology changes and key adding/removal while improves the performance.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)