[
https://issues.apache.org/jira/browse/IGNITE-23457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov reassigned IGNITE-23457:
-----------------------------------------
Assignee: Maksim Zhuravkov
> Sql. Coordinator failed to send close message after query cancellation
> ----------------------------------------------------------------------
>
> Key: IGNITE-23457
> URL: https://issues.apache.org/jira/browse/IGNITE-23457
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Evgeny Stanilovsky
> Assignee: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
>
> Case: _Query was canceled (for some reason, execution timeout or client side
> action) but coordinator failed with sending close message . Need to handle
> such a case and just ignore, no recovery actions are needed here, no errors
> on client side._
> Let`s explain we have a long running query and for some reasons *cancel* is
> triggered, directly after two things are happen: 1. coordinator start to send
> close message into working nodes 2. one or more nodes become unavailable. On
> the basis of our assumptions - NodeLeft event need to be raised but it also
> can be raised _after_ message service error. All such cases need to be
> handled correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
