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

Posted to issues@ignite.apache.org by "Mikhail Efremov (Jira)" <ji...@apache.org> on 2025/12/18 07:22:00 UTC

[jira] [Created] (IGNITE-27387) Properly log cause of exceptionally aborted transactions

Mikhail Efremov created IGNITE-27387:
----------------------------------------

             Summary: Properly log cause of exceptionally aborted transactions
                 Key: IGNITE-27387
                 URL: https://issues.apache.org/jira/browse/IGNITE-27387
             Project: Ignite
          Issue Type: Improvement
            Reporter: Mikhail Efremov


*Description*
Looks like we don't log a reason of exceptional tx abortion. We have to do it in throttled way.

*Motivation*
Logs are critical to trace a reason why user's txes are failed due to internal errors.

*Definition of done*
There are throttled logging added in case of internal errors that leads to tx abort status.



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