conn, util: make opentracing work again (#50551)#50556
Conversation
|
This cherry pick PR is for a release branch and has not yet been approved by triage owners. To merge this cherry pick:
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-7.1 #50556 +/- ##
================================================
Coverage ? 73.4139%
================================================
Files ? 1207
Lines ? 378702
Branches ? 0
================================================
Hits ? 278020
Misses ? 82929
Partials ? 17753 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hawkingrei The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
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.enablenot 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.