You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2017/09/04 10:01:00 UTC

[jira] [Commented] (IGNITE-4931) Safe way for deactivate cluster

    [ https://issues.apache.org/jira/browse/IGNITE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152417#comment-16152417 ] 

Alexey Kuznetsov commented on IGNITE-4931:
------------------------------------------

[~DmitriyGovorukhin] In test _testDeactivationWithPendingTransaction_ we wait transaction to complete, and then proceed deactivation. If we activate clust after deactivation, the result of transaction must be seen (the key-value must exist in cache). 
After deactivation, all cache data got removed, so we must safe ongoing transactions before deactivation, and restart them after activation. Could you change the description of task. May be we should create another task - to restart transactions after re-activation ?

> 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)