[
https://issues.apache.org/jira/browse/IGNITE-28681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-28681:
------------------------------------
Summary: Integrate Operation Context in Ignite internal structures for
async execution (was: Integrate Operation Context in Ignite internals)
> Integrate Operation Context in Ignite internal structures for async execution
> -----------------------------------------------------------------------------
>
> Key: IGNITE-28681
> URL: https://issues.apache.org/jira/browse/IGNITE-28681
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Labels: IEP-143, ise
> Fix For: 2.19
>
>
> According to IEP-143 Unified Operation Context Propagation, Operation Context
> propagation should be integrated into Ignite's internal structures for
> asynchronous task execution, such as GridTimeoutProcessor. These structures
> should automatically capture the operation context of the thread submitting
> the task and restore it before executing the task.
> The following Ignite structures should be considered:
> 1. Starting of a task execution in a separate thread - see
> IgniteUtils#newThread usages
> 2. GridTimeoutProcessor
> 3. Workers that start a single thread for processing data queued by other
> threads . See:
> * DataStreamerImpl
> * DmsDataWriterWorker
> * CommunicationWorker
> * ExchangeWorker
> * SegmentCheckWorker
> * DiscoveryMessageNotifierWorker
> and so on.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
