Mikhail Petrov created IGNITE-29116:
---------------------------------------
Summary: Fix Operation Context propagation for Ignite Compute
Key: IGNITE-29116
URL: https://issues.apache.org/jira/browse/IGNITE-29116
Project: Ignite
Issue Type: Task
Reporter: Mikhail Petrov
Ignite Compute may handle tasks in the same way that thread pools and features
handle executables/listeners: tasks are submitted, stored in an internal
collection, and then started by an arbitrary thread. Therefore, we need to
solve the same Operation Context propagation problem that we solved for Ignite
Futures and thread pools.
Another aspect is that a Compute task may receive signals from other threads,
such as a cluster node left event, and react to them (e.g., by executing the
task's reduce phase). These scenarios should be reviewed to avoid situations
where a task phases are executed with an unexpected Operation Context that does
not belong to the task initiator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
