[
https://issues.apache.org/jira/browse/IGNITE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167931#comment-16167931
]
Ilya Lantukh commented on IGNITE-4931:
--------------------------------------
[~Alexey Kuznetsov],
Tests look good, but you should also specify in ignite.active(boolean) method's
javadoc that it will throw exception in such use case.
> 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). In new tests we should
> run transactions\lock in the same thread as deactivation started
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
