[jira] [Commented] (IGNITE-3164) Add an option to send resulting value instead of entry processor in transactional cache

["Nikolay Tikhonov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296177#comment-15296177 ] 

Nikolay Tikhonov commented on IGNITE-3164:
------------------------------------------

Implemented `IgniteCache.withSendValueToBackup()` behaviour. In this case entry processor creates values to cache only on primary node and  sends they to backup nodes. But we have one more invocation on client node (where {{invoke}} method was called) for value which will be returned from {{invoke}} method. Should we rid the invocation and send resulting value from primary node to client node?

> Add an option to send resulting value instead of entry processor in transactional cache
> ---------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3164
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3164
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>            Assignee: Nikolay Tikhonov
>              Labels: important
>             Fix For: 1.7
>
>
> In some cases user can't guarantee that EP behaves consistently on all nodes. In transactional cache this can lead to inconsistent cache, because we invoke EP on both primary and backup nodes.
> We can add {{withSendValueToBackup()}} flag (naming is arguable) which will override current default behavior.
> We also need to update documentation, especially provide the explanation of EP behavior in atomic and transactional caches.



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