You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Petrov (Jira)" <ji...@apache.org> on 2026/05/15 07:26:00 UTC
[jira] [Assigned] (IGNITE-28681) Integrate Operation Context in Ignite internals
[ https://issues.apache.org/jira/browse/IGNITE-28681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Petrov reassigned IGNITE-28681:
---------------------------------------
Assignee: Mikhail Petrov
> Integrate Operation Context in Ignite internals
> -----------------------------------------------
>
> 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
>
> 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)