[IGNITE-22855] Sql. Missing ClusterNode can be involved into tx enlist

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0-beta1
• Component/s: sql
• Labels: ignite-3
• Epic Link: Processing sql on unstable topology
• Assignee: Unassigned
• Reporter: Evgeny Stanilovsky
• Created: 29/Jul/24 14:01
• Updated: 25/Nov/24 12:13

Description

DistributedQueryManager#sendFragments enlists partitions:

            if (!tx.isReadOnly()) {
                for (MappedFragment mappedFragment : mappedFragments) {
                    enlistPartitions(mappedFragment, tx);
                }
            }

and obtain ClusterNode from topologyService, here:
IgniteRelShuttle#enlist
but node can leave topology at that moment and null will return in such a case.

@Nullable ClusterNode getByConsistentId(String consistentId);

need to cover such a case and re run existing query

Issue Links

• is duplicated by: IGNITE-23454 Sql. Worker node left the cluster during transaction initialization phase
• is part of: IGNITE-22969 Sql. Replanning query on unstable topology
• is part of: IGNITE-23454 Sql. Worker node left the cluster during transaction initialization phase