[
https://issues.apache.org/jira/browse/IGNITE-14015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267856#comment-17267856
]
Taras Ledkov edited comment on IGNITE-14015 at 1/19/21, 12:30 PM:
------------------------------------------------------------------
Merged to
[master|https://github.com/apache/ignite/commit/66f7d6afa738c4e71be3f327a2f8c6fc8523e668]
Cherry-picked to
[ignite-2.10|https://github.com/apache/ignite/commit/462a3cbb8dc7c98ffffbee3335fcfbbec3b1a124]
[~PetrovMikhail], thanks for contribution.
was (Author: tledkov-gridgain):
Merged to
[master|https://github.com/apache/ignite/commit/66f7d6afa738c4e71be3f327a2f8c6fc8523e668]
[~PetrovMikhail], thanks for contribution.
> Tracing SQL: tracing of SELECT queries causes incorrect span inheritance
> ------------------------------------------------------------------------
>
> Key: IGNITE-14015
> URL: https://issues.apache.org/jira/browse/IGNITE-14015
> Project: Ignite
> Issue Type: Bug
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Critical
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Execution of SELECT queries with tracing enabled leaves span related to this
> query in MTC#span variable for user thread. So the trace of next operation
> from the user thread will be inherited from span related to previous query
> execution. We must clear MTC#span thread local variable after query execution
> ends.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
