[ 
https://issues.apache.org/jira/browse/IGNITE-18545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679518#comment-17679518
 ] 

Ignite TC Bot commented on IGNITE-18545:
----------------------------------------

{panel:title=Branch: [pull/10482/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10482/head] Base: [master] : New Tests 
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Compute (Grid){color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=7020160]]
* {color:#013220}IgniteBinaryObjectsComputeGridTestSuite: 
TaskOptionsPropagationTest.testComputeSharedAcrossMultipleThreads - 
PASSED{color}
* {color:#013220}IgniteBinaryObjectsComputeGridTestSuite: 
TaskOptionsPropagationTest.testUserTaskOptionsWithPrecedingSystemTaskExecution 
- PASSED{color}
* {color:#013220}IgniteBinaryObjectsComputeGridTestSuite: 
TaskOptionsPropagationTest.testTaskExecutionOptionsReset - PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=7020237&buildTypeId=IgniteTests24Java8_RunAll]

> Compute "withXXX" modifiers in some cases are not applied to the user compute 
> method call.
> ------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18545
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18545
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Mikhail Petrov
>            Assignee: Mikhail Petrov
>            Priority: Minor
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When the "withXXX" IgniteCompute methods are called, we set the corresponding 
> thread-local parameters that are applied to the first task executed (see 
> IgniteComputeImpl#withName).
> When we run the task, we clear all the thread-local settings that were set 
> earlier.
> Consider the IgniteCompute#affinityCall method.
> During its execution, in some cases we run a system task to get the affinity 
> distribution from other nodes before user task execution (see 
> GridAffinityProcessor#affinityKey and 
> GridAffinityProcessor#affinityInfoFromNode). As a result, the mentioned above 
> modifiers are applied to the system task that requests the affinity 
> distribution but not the user task.
> It seems that the current approach to setting task parameters via 
> thread-local variables is  error-prone and should be refactored.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to