[
https://issues.apache.org/jira/browse/IGNITE-24606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-24606:
---------------------------------------
Description:
If there are just 2 nodes in a cluster and a zone is created with 25 replicas,
then actual assignments will be calculated using group size equal to 2 (as
there are just 2 nodes). So, for assignments, group size is calculated as
min(zone.replicas, cluster.nodesCount). This is by design.
But partition status calculation is performed using just zone.replicas without
any min() operator. So, for the example described here, all partitions will be
declared as READ_ONLY, even though group size is 2, majority is 2 and all nodes
are online, so the state must be just DEGRADED.
We must align partition status calculation with assignments calculation.
> Partition status calculation sometimes uses wrong number of replicas
> --------------------------------------------------------------------
>
> Key: IGNITE-24606
> URL: https://issues.apache.org/jira/browse/IGNITE-24606
> Project: Ignite
> Issue Type: Bug
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> If there are just 2 nodes in a cluster and a zone is created with 25
> replicas, then actual assignments will be calculated using group size equal
> to 2 (as there are just 2 nodes). So, for assignments, group size is
> calculated as min(zone.replicas, cluster.nodesCount). This is by design.
> But partition status calculation is performed using just zone.replicas
> without any min() operator. So, for the example described here, all
> partitions will be declared as READ_ONLY, even though group size is 2,
> majority is 2 and all nodes are online, so the state must be just DEGRADED.
> We must align partition status calculation with assignments calculation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
