[
https://issues.apache.org/jira/browse/IGNITE-23454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich resolved IGNITE-23454.
-----------------------------------------
Resolution: Duplicate
> Sql. Worker node left the cluster during transaction initialization phase
> -------------------------------------------------------------------------
>
> Key: IGNITE-23454
> URL: https://issues.apache.org/jira/browse/IGNITE-23454
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-3
>
> Case: _Partitions are enlisted alongside the ClusterNode which is considered
> to be the owner of the primary replica of the particular partition. Before
> enlistment, ClusterNode is resolved by consistentId of the replica, which was
> returned from PlacementDriver. If at the moment of resolution node with given
> consistentId has left the cluster, query execution must be restarted from the
> Mapping phase. Worth to mention, that new assignment must be acquired from
> PlacementDriver._
> Definition of done:
> 1. Correctly process the case when node by consistentId is unavailable.
> 2. Check tx enlist process with consistentId change (suppose we have
> explicit tx and sequential queries with topology change between execution)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
