[
https://issues.apache.org/jira/browse/IGNITE-27385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Efremov updated IGNITE-27385:
-------------------------------------
Description:
*Description*
Now if a transaction's result is {{ABORTED}} we can't actually distinct a
reason: was it user's rollback or there was an internal error that leads to it?
So the main goal of the ticket split currently existing state
{{TxState#ABORTED}} on {{TxState#ABORTED_EXCEPTIONALLY}} and
{{{}TxState#ROLLEDBACK{}}}, the first is for internal error cases and the last
for user's reaction cases such as manual rollback and kill calls.
*Motivation*
We need more verbose and informative transactions results and logs.
*Definition of done*
# On user's rollback or kill commands now txs' states should be
{{{}TxState#ROLLEDBACK{}}}.
# On any internal exceptional situation we have to apply
\{{TxState#ABORTED_EXCEPTIONALLY}} instead.
was:
*Description*
Now if a transaction's result is {{ABORTED}} we can't actually distinct a
reason: was it user's rollback or there was an internal error that leads to it?
So the main goal of the ticket split currently existing state
{{TxState#ABORTED}} on {{TxState#ABORTED_EXCEPTIONALLY}} and
{{{}TxState#ROLLEDBACK{}}}, the first is for internal error cases and the last
for user's reaction cases such as manual rollback and kill calls.
*Motivation*
We need more verbose and informative transactions results and logs.
*Definition of done*
# On user's rollback or kill commands now txs' states should be{{{}
TxState#ROLLEDBACK{}}}.
# On any internal exceptional situation we have to apply{{
TxState#ABORTED_EXCEPTIONALLY}} instead.
> Split TxState#ABORTED for user rolled back and exceptionally aborted states
> ---------------------------------------------------------------------------
>
> Key: IGNITE-27385
> URL: https://issues.apache.org/jira/browse/IGNITE-27385
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Efremov
> Priority: Major
> Labels: ignite-3
>
> *Description*
> Now if a transaction's result is {{ABORTED}} we can't actually distinct a
> reason: was it user's rollback or there was an internal error that leads to
> it? So the main goal of the ticket split currently existing state
> {{TxState#ABORTED}} on {{TxState#ABORTED_EXCEPTIONALLY}} and
> {{{}TxState#ROLLEDBACK{}}}, the first is for internal error cases and the
> last for user's reaction cases such as manual rollback and kill calls.
> *Motivation*
> We need more verbose and informative transactions results and logs.
> *Definition of done*
> # On user's rollback or kill commands now txs' states should be
> {{{}TxState#ROLLEDBACK{}}}.
> # On any internal exceptional situation we have to apply
> \{{TxState#ABORTED_EXCEPTIONALLY}} instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
