You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2017/08/04 16:22: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=16114579#comment-16114579 ] 

Dmitriy Pavlov commented on IGNITE-4931:
----------------------------------------

Following tests were muted with link to this issue:
 ClusterStatePartitionedSelfTest.testDeactivationWithPendingLock   
 ClusterStatePartitionedSelfTest.testDeactivationWithPendingTransaction 
 ClusterStateReplicatedSelfTest.testDeactivationWithPendingLock 
 ClusterStateReplicatedSelfTest.testDeactivationWithPendingTransaction 

> 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
>              Labels: MakeTeamcityGreenAgain, Muted_test
>             Fix For: 2.2
>
>
> 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)