You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Yakov Zhdanov (JIRA)" <ji...@apache.org> on 2016/09/13 11:44:20 UTC

[jira] [Assigned] (IGNITE-104) Need to enable thread-per-partition mode for atomic caches

     [ https://issues.apache.org/jira/browse/IGNITE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yakov Zhdanov reassigned IGNITE-104:
------------------------------------

    Assignee: Yakov Zhdanov

> Need to enable thread-per-partition mode for atomic caches
> ----------------------------------------------------------
>
>                 Key: IGNITE-104
>                 URL: https://issues.apache.org/jira/browse/IGNITE-104
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>            Reporter: Dmitriy Setrakyan
>            Assignee: Yakov Zhdanov
>            Priority: Critical
>
> Currently messages are processed in any order for atomic caches. We can add ordered processing by assigning a thread per partition. This way we will be able to remove any locking as well.
> {{Cache.invoke()}} method would be able to invoke the EntryProcessor on primary and backup independently. Right now we only invoke the EntryProcessor only on the primary node and the send the computed value to the backup node, which may be expensive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)