-
Notifications
You must be signed in to change notification settings - Fork 6.1k
*: refactor CheckFlightRecorderDumpTrigger API and capture trace ID missing event #64569
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @tiancaiamao. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. 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-sigs/prow repository. |
|
/retest |
Codecov Report❌ Patch coverage is Please upload reports for the commit 466b2ea to get more accurate results. Additional details and impacted files@@ Coverage Diff @@
## master #64569 +/- ##
================================================
+ Coverage 74.6905% 74.7966% +0.1060%
================================================
Files 1888 1889 +1
Lines 515097 516091 +994
================================================
+ Hits 384729 386019 +1290
+ Misses 106545 106308 -237
+ Partials 23823 23764 -59
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
@tiancaiamao: The following test failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
|
@tiancaiamao: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
What problem does this PR solve?
Issue Number: close #64008
Problem Summary:
I want to know whether there are some place calling client-go API, without passing trace ID.
All the caller should pass the trace ID from tidb to tikv to archive distributed tracing.
What changed and how does it work?
I add a flight recorder dump trigger to client-go, if the caller are not passing trace ID, print the call stack.
So we can found all those trace event using this command:
CheckFlightRecorderDumpTrigger API current cannot be used by client-go.
The function old signature is
And it's changed to
It means in the past, we pass
*DumpTriggerConfigto the callee and the callee compare the config with its state.But
*DumpTriggerConfigis defined is tidb, not client-go, so client-go cannot use this API.Now, we let the callee provide it state, and the dump trigger config change that state.
Check List
Tests
Together with #64341, we can find some internal session not passing trace ID to client-go
For example, it find this stack:
And turn out to be casused by here https://github.com/tikv/client-go/blob/1264c12785957baf4ba745368bf0b853520de711/txnkv/transaction/prewrite.go#L171-L183
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.