[ https://issues.apache.org/jira/browse/IGNITE-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk updated IGNITE-1553: ------------------------------------- Fix Version/s: (was: 2.6) > 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 > > 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:java} > 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. > > store prepare works on primary nodes only -- This message was sent by Atlassian JIRA (v7.6.3#76005)