You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Daradur (JIRA)" <ji...@apache.org> on 2018/03/05 09:25:00 UTC

[jira] [Updated] (IGNITE-1553) Optimize transaction prepare step when store is enabled

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

Vyacheslav Daradur updated IGNITE-1553:
---------------------------------------
    Fix Version/s: 2.5

> Optimize transaction prepare step when store is enabled
> -------------------------------------------------------
>
>                 Key: IGNITE-1553
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1553
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: ignite-1.4
>            Reporter: Alexey Goncharuk
>            Assignee: Alexey Kuznetsov
>            Priority: Major
>              Labels: important
>             Fix For: 2.5
>
>
> Currently entries are enlisted in a database transaction after grid transaction is in PREPARED state. We can do this in parallel in the following fashion (pseudo-code):
> {code}
> fut = tx.prepareAsync();
> db.write(tx.writes());
> fut.get();
> try {
>     db.commit();
>     
>     tx.commit();
> }
> catch (Exception e) {
>     tx.rollback();
> }
> {code}
> If this approach is applied, we should be able to reduce latency for transactions when write-through is enabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)