You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2024/01/11 13:51:00 UTC
[jira] [Updated] (IGNITE-21239) Take into account SUSPENDED transaction state for some operations
[ https://issues.apache.org/jira/browse/IGNITE-21239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-21239:
---------------------------------------
Description:
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)
was:
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)
> 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
> Priority: Major
> Labels: ise
>
> 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)