You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/03 10:03:06 UTC
[jira] [Updated] (IGNITE-3471) Do not send previous value to client
node for invoke() when possible
[ https://issues.apache.org/jira/browse/IGNITE-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-3471:
------------------------------------
Fix Version/s: (was: 2.8)
2.9
> Do not send previous value to client node for invoke() when possible
> --------------------------------------------------------------------
>
> Key: IGNITE-3471
> URL: https://issues.apache.org/jira/browse/IGNITE-3471
> Project: Ignite
> Issue Type: Task
> Components: cache
> Affects Versions: 1.4
> Reporter: Alexey Goncharuk
> Priority: Major
> Fix For: 2.9
>
> Attachments: CacheEntryProcessorTxSelfTest.java
>
>
> Currently for invoke() or invokeAll() methods we send previous cache value to near node and apply EntryProcessor locally to get a return value. This can induce a significant overhead when cache value is much larger than entry processor result.
> For many cases this can be avoided, e.g.
> {code}
> try (tx = txStart()) {
> cache.invoke(key, EP); // No need to send previous value to client in this case.
> tx.commit();
> }
> {code}
> Note that we need to add additional handling of such a case:
> {code}
> try (tx = txStart()) {
> cache.invoke(key, EP); // No need to send previous value to client in this case.
> cache.get(key); // This should actually get the current cache value from primary node and apply an entry processor locally to get the updated value.
> tx.commit();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)