[
https://issues.apache.org/jira/browse/IGNITE-23378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Khitrin updated IGNITE-23378:
------------------------------------
Affects Version/s: 3.0
> Aimem: READ_ONLY partitions after 1 node restart in 2 nodes cluster
> -------------------------------------------------------------------
>
> Key: IGNITE-23378
> URL: https://issues.apache.org/jira/browse/IGNITE-23378
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 3.0, 3.0.0-beta1
> Environment: 2 nodes cluster running on single physical machine
> Reporter: Igor
> Priority: Major
> Labels: ignite-3
> Attachments: server_logs.zip
>
>
> *Steps to reproduce:*
> # Create 2 nodes cluster with 1 CMG node (node_0 - CMG,node_1).
> # Create zone with replication equals to amount of nodes (2).
> # Create 1 table inside the zone.
> # Insert 10 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)
> # Start killed node.
> # Using REST API await *physical* topology has 2 alive nodes.
> # Using REST API await *logical* topology has 2 alive nodes.
> # Await all tables*partitions*nodes local state is "HEALTHY" (by connecting
> to REST of node_0).
> # Await all tables*partitions*nodes local state is "AVAILABLE" (by
> connecting to REST of node_0).
> *Expected:*
> All partitions become "AVAILABLE".
> *Actual:*
> Partitions in states: "AVAILABLE" and "READ_ONLY"
> [^server_logs.zip]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
