ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Setrakyan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-104) Need to enable thread-per-partition mode for atomic caches
Date Mon, 03 Aug 2015 22:59:04 GMT

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

Dmitriy Setrakyan updated IGNITE-104:
-------------------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: IGNITE-1191

> 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: Valentin Kulichenko
>            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)

Mime
View raw message