client-go: attach request source with retry info for coprocessor#46509
client-go: attach request source with retry info for coprocessor#46509ti-chi-bot[bot] merged 2 commits intopingcap:masterfrom
Conversation
Signed-off-by: you06 <you1474600@gmail.com>
|
Hi @you06. 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/test-infra repository. |
|
/ok-to-test |
|
/test all |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #46509 +/- ##
================================================
- Coverage 73.3755% 72.4961% -0.8794%
================================================
Files 1303 1332 +29
Lines 394509 404591 +10082
================================================
+ Hits 289473 293313 +3840
- Misses 86640 92776 +6136
- Partials 18396 18502 +106
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
/retest |
| } else { | ||
| s.sessionVars.RequestSourceType = stmtLabel | ||
| } | ||
| s.sessionVars.RequestSourceType = stmtLabel |
There was a problem hiding this comment.
This is a tiny fix because coprocessor will read request source from the session variables.
|
/retest |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ekexium, zyguan 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 |
|
/retest |
|
/merge |
|
@cfzjywxk: We have migrated to builtin Please use
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 ti-community-infra/tichi repository. |
|
/retest |
|
/test all |
|
@you06: 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/test-infra repository. I understand the commands that are listed here. |
|
In response to a cherrypick label: new pull request created to branch |
|
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
) (#47003) * client-go: attach request source with retry info for coprocessor (#46509) (#46706) close #46514 * restore bazelversiong Signed-off-by: you06 <you1474600@gmail.com> * remove unused field Signed-off-by: you06 <you1474600@gmail.com> * update client-go Signed-off-by: you06 <you1474600@gmail.com> --------- Signed-off-by: you06 <you1474600@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io> resolve conflict Signed-off-by: you06 <you1474600@gmail.com>
…gcap#46706) (pingcap#47003) (pingcap#6) * client-go: attach request source with retry info for coprocessor (pingcap#46509) (pingcap#46706) close pingcap#46514 * restore bazelversiong Signed-off-by: you06 <you1474600@gmail.com> * remove unused field Signed-off-by: you06 <you1474600@gmail.com> * update client-go Signed-off-by: you06 <you1474600@gmail.com> --------- Signed-off-by: you06 <you1474600@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io> Signed-off-by: you06 <you1474600@gmail.com> Co-authored-by: you06 <you1474600@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
What problem does this PR solve?
Issue Number: close #46514
Problem Summary:
What is changed and how it works?
Update client-go which will attach the request source with retry info for KV requests. This PR set the required options for coprocessor to enable the extra retry info.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.