Incorrect transaction state when client node reconnects

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Incorrect transaction state when client node reconnects

voipp
Hi, Igntrs!

Client reconnect cause transactions rollback in
IgniteTxManager#onDisconnected.

But it doesn’t change transaction state to ROLLING_BACK and ROLLED_BACK.

Thus every transaction, after client node reconnects, has got ACTIVE
status, which seems incorrect.

I added PR where you can find test, showing incorrect status: [1]

Should we change status to ROLLING_BACK and then to ROLLED_BACK right after
rollback ?

[1]
https://github.com/apache/ignite/pull/3079/files#diff-04cb3a1c00a0168abc210484392031bbR396

--

*Best Regards,*

*Kuznetsov Aleksey*