[IGNITE-15732] Thin client: Tx can fail if there are concurrent tx rollbacks by timeout

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.12
• Labels: ise
• Release Note: Thin client: Fixed transaction failure after concurrent previous transaction rollback on the same worker
• Ignite Flags: Release Notes Required
• Assignee: Aleksey Plekhanov
• Reporter: Aleksey Plekhanov
• Created: 12/Oct/21 14:33
• Updated: 27/Oct/21 07:07
• Resolved: 27/Oct/21 06:56

Description

Due to race between timeout worker and client-connector workers there can be situations when some transaction is processed by client-connector worker and concurrently rolled back by timeout worker. In this case, threadMap can still contain the reference to this transaction but the transaction state is already set to "ROLLED_BACK", for such a state client-connector worker does not suspend the transaction and can proceed to the next request, which uses another transaction. When resuming this second transaction there is an exception thrown, since IgniteTxManager#threadMap is not cleared yet for the current worker thread:

org.apache.ignite.client.ClientException: Ignite failed to process request [103]: Thread already has started a transaction. (server status code [1])

 

Issue Links

• links to: GitHub Pull Request #9504