conn, util: make opentracing
work again (#50551)
#50556
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #50551
What problem does this PR solve?
Issue Number: close #50508
Problem Summary: Caused by #40825, miss root span for opentracing tools.
What changed and how does it work?
Check List
Tests
Start a TiDB cluster as
opentracing.enable
not work after v7.1.0 #50508 said, and use JaegerUI to get trace info success.Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.