[
https://issues.apache.org/jira/browse/IGNITE-28681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18082515#comment-18082515
]
Ignite TC Bot commented on IGNITE-28681:
----------------------------------------
{panel:title=Branch: [pull/13148/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13148/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Security{color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=9083509]]
* {color:#013220}SecurityTestSuite:
OperationContextAttributesTest.testIgniteThread - PASSED{color}
* {color:#013220}SecurityTestSuite:
OperationContextAttributesTest.testTimeoutWorker - PASSED{color}
* {color:#013220}SecurityTestSuite:
OperationContextAttributesTest.testContextAwareQueue - PASSED{color}
* {color:#013220}SecurityTestSuite:
OperationContextAttributesTest.testContextAwareDelayQueue - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9083557&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9083557
rerunBuildIds=9084077,9084079,9084081,9084083{color}
> 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
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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 mechanisms 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)
