Igor created IGNITE-22725:
-----------------------------
Summary: (flaky) aimem: node doesn't recover after data clean and
goes into state DEGRADED
Key: IGNITE-22725
URL: https://issues.apache.org/jira/browse/IGNITE-22725
Project: Ignite
Issue Type: Bug
Components: persistence
Affects Versions: 3.0.0-beta2
Environment: 3 distributed nodes (with 1 CMG), storage AIMEM
Reporter: Igor
Attachments: server_logs.zip
*{color:#de350b}This issue sometimes is replaced by
https://issues.apache.org/jira/browse/IGNITE-22724{color}*
*Steps to reproduce:*
# Create 3 nodes cluster with 1 CMG node (node_0 - CMG,node_1,node_2).
# 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. (kill node_1)
# Clean data in work directory of killed node (node_1).
# Start killed node.
# 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" (by connecting to
REST of node_2).
# Await all tables*partitions*nodes local state is "AVAILABLE" (by connecting
to REST of node_2).
*Expected:*
All partitions become "AVAILABLE".
*Actual:*
Partitions in states: "AVAILABLE" and "DEGRADED".[^server_logs.zip]
*Comments:*
This test works fine with aipersist storage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
