[jira] [Created] (IGNITE-21239) Take into account SUSPENDED transaction state for some operations

["Aleksey Plekhanov (Jira)" <ji...@apache.org>]

Aleksey Plekhanov created IGNITE-21239:
------------------------------------------

             Summary: Take into account SUSPENDED transaction state for some operations
                 Key: IGNITE-21239
                 URL: https://issues.apache.org/jira/browse/IGNITE-21239
             Project: Ignite
          Issue Type: Bug
            Reporter: Aleksey Plekhanov


There are some operations in Ignite, which check only \{{ACTIVE}} transaction state, but looks like {{SUSPENDED}} state should also match the condition for these operations.

Transaction state {{SUSPENDED}} is almost the same as \{{ACTIVE}}, but detached from a thread.

Examples of methods where {{SUSPENDED}} state should be threated the same way as {{{}ACTIVE{}}}:
 * {\{GridCachePartitionExchangeManager#dumpLongRunningOperations0}}
 * {{IncrementalSnapshotMarkWalFuture#init}}
 * {{TransactionMetricsAdapter#txHoldingLockNum}} (here condition is strange, perhaps should be rewriten)
 * {{IgniteTxManager#salvageTx}} (not sure about this method, further analysis required) 



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