You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/06 08:14:18 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16038344#comment-16038344 ]
ASF GitHub Bot commented on IGNITE-1553:
----------------------------------------
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/2091
IGNITE-1553 Optimize transaction prepare step when store is enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-1553
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2091.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2091
----
----
> 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
> 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}
> 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
(v6.3.15#6346)