You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2023/05/15 12:20:00 UTC

[jira] [Commented] (IGNITE-19343) Enable some muted test from DistributionZoneAwaitDataNodesTest

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

Alexander Lapin commented on IGNITE-19343:
------------------------------------------

[~Sergey Uttsel] LGTM, thank you!

> Enable some muted test from DistributionZoneAwaitDataNodesTest
> --------------------------------------------------------------
>
>                 Key: IGNITE-19343
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19343
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Mirza Aliev
>            Assignee: Sergey Uttsel
>            Priority: Blocker
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> h3. *Motivation*
> When IGNITE-18756 was developed, some of the test were disabled, because we thought that after introduction of {{StandaloneMetaStorageManager}} it will be impossible to test some concurrent scenarios with MetaStorage. But seems that is it possible, see {{DistributionZoneManagerScaleUpTest#testScaleUpDidNotChangeDataNodesWhenTriggerKeyWasConcurrentlyChanged}}
> Disabled tests: 
> {{{}DistributionZoneAwaitDataNodesTest#testRemoveZoneWhileAwaitingDataNodes{}}}, 
> {{DistributionZoneAwaitDataNodesTest#testScaleUpScaleDownAreChangedWhileAwaitingDataNodes}}
> h3. *Definition of Done*
> testRemoveZoneWhileAwaitingDataNodes and testScaleUpScaleDownAreChangedWhileAwaitingDataNodes are enabled.
> h3. *Implementation Notes*
> DistributedConfigurationStorage is used in BaseDistributionZoneManagerTest to fix an issue when metaStorageManager and zonesConfiguration use different storage and have different storage revisions. So https://issues.apache.org/jira/browse/IGNITE-19342 is partly implemented.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)