[
https://issues.apache.org/jira/browse/IGNITE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936617#comment-14936617
]
Semen Boikov commented on IGNITE-104:
-------------------------------------
Update for this task: the main reason to implement thread-per-partition was
support continuous queries notifications when primary node fails (IGNITE-426).
But now to support continuous queries we decided to use another approach which
does not require thread-per-partition model, so work on this task is postponed.
> 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: Semen Boikov
> 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)
