[jira] [Commented] (IGNITE-24467) HA: Filtered nodes are not applied after automatic reset

[" Kirill Sizov (Jira)" <ji...@apache.org>]

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

 Kirill Sizov commented on IGNITE-24467:
----------------------------------------

Same issue is with the storage profiles

> HA: Filtered nodes are not applied after automatic reset
> --------------------------------------------------------
>
>                 Key: IGNITE-24467
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24467
>             Project: Ignite
>          Issue Type: Bug
>            Reporter:  Kirill Sizov
>            Priority: Major
>              Labels: ignite-3
>
> See {{ItHighAvailablePartitionsRecoveryByFilterUpdateTest.testResetAfterChangeFilters}} - the test that covers this scenario.
> *Precondition*
>  - Create an HA zone with a filter that allows nodes A, B and C.
>  - Make sure {{partitionDistributionResetTimeout}} is high enough not to trigger before the following actions happen
>  - Stop nodes B and C
>  - Change zone filter to allow nodes D, E and F. These new nodes should be up and running
>  - Change {{partitionDistributionResetTimeout}} to a smaller value or 0 to trigger automatic reset
> *Result*
> The partition remains on node A
>  
> *Expected result*
> The partition is moved to D, E and F as per the filter
> *Implementation details*
> Zone filter change creates new pending = (D,E,F). But automatic reset, that is triggered after {{{}partitionDistributionResetTimeout{}}}, changes pending to (force, A), planned=(), thus losing any information about nodes D, E and F 



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