You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2023/05/02 10:17:00 UTC

[jira] [Updated] (IGNITE-19336) Transaction initiator can hang after transaction timeout.

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

Vladimir Steshin updated IGNITE-19336:
--------------------------------------
    Summary: Transaction initiator can hang after transaction timeout.  (was: No action or warning after transaction timeout on commit phase.)

> Transaction initiator can hang after transaction timeout.
> ---------------------------------------------------------
>
>                 Key: IGNITE-19336
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19336
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladimir Steshin
>            Priority: Minor
>         Attachments: TransactionLostResponsesTimeoutTest.java
>
>
> Issue: _Transaction#commit()_ can hang forever if some transaction responses (like finish response or prepare response) are lost or delayed. See [1].
> If transaction delays for too long, user should expect a timeout and returned control to the application. 
> There is a point [2]. Probably we can't rollback on commit phase. But we might not rollback, only warn user of long commit, complete the futures and, for example, suggest an investigation.
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency
> [2] https://issues.apache.org/jira/browse/IGNITE-6181



--
This message was sent by Atlassian Jira
(v8.20.10#820010)