[
https://issues.apache.org/jira/browse/IGNITE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154962#comment-16154962
]
Alexey Kuznetsov edited comment on IGNITE-4931 at 9/7/17 9:08 AM:
------------------------------------------------------------------
[~DmitriyGovorukhin] 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'. Perhaps, it would be better off prohibit
user start deactivation when transaction\lock is in progress ?
was (Author: alexey kuznetsov):
[~DmitriyGovorukhin] 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'. Perhaps, it would be better off prohibit
user start deactivation when transaction\lock is in progress ?
> 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
>
>
> 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).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
