[
https://issues.apache.org/jira/browse/IGNITE-22855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov resolved IGNITE-22855.
---------------------------------------
Resolution: Invalid
This ticket seems to be not relevant anymore. The only usage of
{{ClusterNodeResolver#getByConsistentId}} in sql module is in tests.
> Sql. Missing ClusterNode can be involved into tx enlist
> -------------------------------------------------------
>
> Key: IGNITE-22855
> URL: https://issues.apache.org/jira/browse/IGNITE-22855
> Project: Ignite
> Issue Type: Bug
> Components: sql ai3
> Affects Versions: 3.0.0-beta1
> Reporter: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-3
>
> DistributedQueryManager#sendFragments enlists partitions:
> {noformat}
> if (!tx.isReadOnly()) {
> for (MappedFragment mappedFragment : mappedFragments) {
> enlistPartitions(mappedFragment, tx);
> }
> }
> {noformat}
> and obtain ClusterNode from topologyService, here:
> IgniteRelShuttle#enlist
> but node can leave topology at that moment and *null* will return in such a
> case.
> {noformat}
> @Nullable ClusterNode getByConsistentId(String consistentId);
> {noformat}
> need to cover such a case and re run existing query
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
