[ 
https://issues.apache.org/jira/browse/IGNITE-24509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mirza Aliev updated IGNITE-24509:
---------------------------------
    Epic Link: IGNITE-23438

> HA: restarted node cannot get null value after recovered availability
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-24509
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24509
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Mirza Aliev
>            Priority: Major
>              Labels: ignite-3
>
> See 
> {{ItHighAvailablePartitionsRecoveryTest#testNodeStateCleanupAfterRestartInHaMode}}
>  - the test that covers this scenario.
> *Precondition*
>      *   Create a zone in HA mode with 7 nodes (A, B, C, D, E, F, G).
>      *   Insert data and wait for replication to all nodes.
>      *   Stop a majority of nodes (A, B, C, D).
>      *   Wait for the partition to become available on the remaining nodes 
> (E, F, G).
>      *   Start node A.
>      *   Verify that node A cleans up its state.
> *Result*
> InternalTable#get on the restarted node is timed out
>  
> *Expected result*
> InternalTable#get on the restarted node returns null.
> Also tests 
> {{ItHighAvailablePartitionsRecoveryByFilterUpdateTest#testNodesWaitForLastNodeFromChainToComeBackOnlineAfterMajorityStops}}
>  and 
> {{ItHighAvailablePartitionsRecoveryByFilterUpdateTest#testNodesWaitForNodesFromGracefulChainToComeBackOnlineAfterMajorityStops}}
>  fail with the similar behaviour 



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

Reply via email to