Vadim Pakhnushev created IGNITE-24910:
-----------------------------------------
Summary: ItSqlKillCommandTest#killComputeJobFromRemote is flaky
Key: IGNITE-24910
URL: https://issues.apache.org/jira/browse/IGNITE-24910
Project: Ignite
Issue Type: Bug
Components: compute
Reporter: Vadim Pakhnushev
Assignee: Vadim Pakhnushev
On a rare occasion kill query for the compute job is not applied (that is,
{{ResultSet#wasApplied}} returns {{false}}).
This happens when the remote compute job is submitted from node1 to node2 and
cancel query is executed on node3. In this case {{ExecutionManager}} on node3
doesn't contain the execution so the {{ComputeComponentImpl}} broadcasts the
cancel request to node1 and node2.
Node1 holds a {{RemoteJobExecution}} which sends a message to the node2.
Node2 holds a {{DelegatingJobExecution}}.
One of the requests succeeds and cancels the job, returning {{true}}, other
returns {{false}}.
The broadcast method in the {{ComputeMessaging}} completes a result future with
the first received response which could happen to be {{false}}. When {{true}}
response arrives, the future is already complete and so the result of the
cancel on node3 is {{false}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
