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 Govorukhin (JIRA)" <ji...@apache.org> on 2019/01/05 10:42:00 UTC

[jira] [Commented] (IGNITE-10809) IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3 fails in master

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

Dmitriy Govorukhin commented on IGNITE-10809:
---------------------------------------------

[~sergey-chugunov] Is your fix the final fix? Maybe we should refactor test?

> IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3 fails in master
> ----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-10809
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10809
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Chugunov
>            Assignee: Sergey Chugunov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> Test logic involves independent activation two sets of nodes and then their join into a single cluster.
> After introducing BaselineTopology concept in 2.4 version this action became prohibited to enforce data integrity.
> Test should be refactored to take this into account.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)