[
https://issues.apache.org/jira/browse/IGNITE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-4931:
-------------------------------------
Description:
Currently deactivation process, started after transaction start or cache lock
on key hangs waiting transaction end\ cache unlock. Closing
transaction\unlocking the lock leads to excpetion when deactivation is in
progress. It looks like 'deadlock'.
So, expected behaviour: starting deactivation should lead to excpetion if
transaction is in progress or cache key is locked.
Exception should be thrown like in case when we start cache and transaction is
in progress (see checkEmptyTransactions method)
was:We must provide safe way for deactivate cluster, i mean we must wait
while all cache operation, transaction and etc. comleted before start
deactivation process, in current implementation we do not wait while
transaction comlete, (forcibly stop cache during transaction).
> Safe way for deactivate cluster
> -------------------------------
>
> Key: IGNITE-4931
> URL: https://issues.apache.org/jira/browse/IGNITE-4931
> Project: Ignite
> Issue Type: Task
> Components: general
> Affects Versions: 2.0
> Reporter: Dmitriy Govorukhin
> Assignee: Alexey Kuznetsov
> Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.3
>
>
> Currently deactivation process, started after transaction start or cache lock
> on key hangs waiting transaction end\ cache unlock. Closing
> transaction\unlocking the lock leads to excpetion when deactivation is in
> progress. It looks like 'deadlock'.
> So, expected behaviour: starting deactivation should lead to excpetion if
> transaction is in progress or cache key is locked.
> Exception should be thrown like in case when we start cache and transaction
> is in progress (see checkEmptyTransactions method)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
