You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer these questions before submitting your issue.
Why do you submit this issue?
Question or discussion
Bug
Requirement
Feature or performance improvement
Requirement or improvement
The picture below is from a tracing in Sharding-Sphere:
There are 4 threads appear in this tracing: the main thread, Sharding-Sphere-0, Sharding-Sphere-1, Sharding-Sphere-2.
The tracing order in main thread is correct: parsing -> getConnection -> executeSQL -> close.
But it's disordered between threads: Sharding-Sphere-0, Sharding-Sphere-1, Sharding-Sphere-2 should happen after getConnection while before close.
I believe skywalking didn't sort tracing beween threads, and this kind of sort is the requirement.
The text was updated successfully, but these errors were encountered:
wu-sheng
added
bug
Something isn't working and you are sure it's a bug!
TBD
To be decided later, need more discussion or input.
backend
OAP backend related.
labels
Sep 11, 2018
Please answer these questions before submitting your issue.
Requirement or improvement
The picture below is from a tracing in Sharding-Sphere:
There are 4 threads appear in this tracing: the main thread, Sharding-Sphere-0, Sharding-Sphere-1, Sharding-Sphere-2.
The tracing order in main thread is correct: parsing -> getConnection -> executeSQL -> close.
But it's disordered between threads: Sharding-Sphere-0, Sharding-Sphere-1, Sharding-Sphere-2 should happen after getConnection while before close.
I believe skywalking didn't sort tracing beween threads, and this kind of sort is the requirement.
The text was updated successfully, but these errors were encountered: