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/04/20 15:57:00 UTC

[jira] [Updated] (IGNITE-19336) No action or warning after transaction timeout on commit phase.

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

Vladimir Steshin updated IGNITE-19336:
--------------------------------------
    Attachment: TransactionLosesFinishResponsesTimeoutTest.java

> No action or warning after transaction timeout on commit phase.
> ---------------------------------------------------------------
>
>                 Key: IGNITE-19336
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19336
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladimir Steshin
>            Priority: Minor
>         Attachments: TransactionLosesFinishResponsesTimeoutTest.java
>
>
> Regarding [1], during a transaction some conversation messages can be lost or delayed. Like the lock response, prepare response or finish responses. If transaction delays for long, user should expect a timeout and returned control to the application. However, after the prepare phase _Transaction#commit()_ can hang forever. 
> 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)