[
https://issues.apache.org/jira/browse/IGNITE-22517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-22517:
--------------------------
Environment: 3 nodes cluster (1 CMG node) (was: 3 node cluster (1 CMG
node))
> Partitions stay DEGRADED after node replacement in 3 node cluster
> -----------------------------------------------------------------
>
> Key: IGNITE-22517
> URL: https://issues.apache.org/jira/browse/IGNITE-22517
> Project: Ignite
> Issue Type: Bug
> Components: general, networking, persistence
> Affects Versions: 3.0.0-beta2
> Environment: 3 nodes cluster (1 CMG node)
> Reporter: Igor
> Priority: Major
> Labels: ignite-3
> Attachments: CMG node.zip, alive node.zip, killed node.zip,
> replacement for killed node-1.zip
>
>
> *Steps to reproduce:*
> # Create 3 nodes cluster with 1 CMG node.
> # Create zone with replication equals to amount of nodes (3).
> # Create 10 tables inside the zone.
> # Insert 100 rows in every table.
> # Await all tables*partitions*nodes local state is "HEALTHY"
> # Await all tables*partitions*nodes global state is "AVAILABLE"
> # Kill non CMG node with kill -9.
> # Create new node and attach it to cluster instead of the killed one (update
> lookup configs of alive nodes to allow them find).
> # Using REST API await *physical* topology has 3 alive nodes.
> # Using REST API await *logical* topology has 3 alive nodes.
> # Await all tables*partitions*nodes local state is "HEALTHY".
> # Await all tables*partitions*nodes global state is "AVAILABLE".
> *Expected:*
> All partitions become "AVAILABLE".
> *Actual:*
> Partitions in different states: "AVAILABLE" and "DEGRADED".
> The logs are in attachment.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
