[
https://issues.apache.org/jira/browse/IGNITE-16705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-16705:
------------------------------------
Labels: iep-100 ignite-3 (was: ignite-3)
> Resolve Compute futures that had no chance to be executed on node stop
> ----------------------------------------------------------------------
>
> Key: IGNITE-16705
> URL: https://issues.apache.org/jira/browse/IGNITE-16705
> Project: Ignite
> Issue Type: Improvement
> Components: compute
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: iep-100, ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We execute Compute jobs using a separate ExecutorService. It has a bounded
> number of threads and an unbounded work queue. It might happen that on node
> stop some tasks are not executed, so their corresponding futures never get
> resolved.
> The standard CompletableFuture does not provide any built-in mechanisms for
> solving this problem.
> We should track the futures ourselves and cancel the unresolved ones after
> stopping the executor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
