Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.0.0-beta2
-
None
-
3 nodes cluster (1 CMG node)
-
Docs Required, Release Notes Required
Description
This issue is replaced by https://issues.apache.org/jira/browse/IGNITE-22553 from time to time.
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.
Attachments
Attachments
Issue Links
- relates to
-
IGNITE-22553 Internal Server Error after node replacement in 3 node cluster
- Open
- supercedes
-
IGNITE-22376 RestAPI get logical topology freeze if 1 node was replaced in 3 nodes cluster
- Resolved