[
https://issues.apache.org/jira/browse/IGNITE-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev updated IGNITE-24353:
--------------------------------------
Description:
When submitting compute job through the client and the worker node leaves the
cluster, the job is restarted on another node with the failover mechanism, but
the {{JobExecution.node()}} method returns initial worker node.
Ideally the method should be asynchronous and ask for the current node each
time.
We could also send the worker node along with the result so it will at least
provide a correct node after the job has completed.
was:When submitting compute job through the client and the worker node leaves
the cluster, the job is restarted on another node with the failover mechanism,
but the {{JobExecution.node()}} method returns initial worker node.
> Client job execution object doesn't follow failover
> ---------------------------------------------------
>
> Key: IGNITE-24353
> URL: https://issues.apache.org/jira/browse/IGNITE-24353
> Project: Ignite
> Issue Type: Bug
> Components: compute, thin client
> Reporter: Vadim Pakhnushev
> Assignee: Vadim Pakhnushev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
>
> When submitting compute job through the client and the worker node leaves the
> cluster, the job is restarted on another node with the failover mechanism,
> but the {{JobExecution.node()}} method returns initial worker node.
> Ideally the method should be asynchronous and ask for the current node each
> time.
> We could also send the worker node along with the result so it will at least
> provide a correct node after the job has completed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
