infoschema,metrics: use tidb_tikvclient_request_seconds_bucket to get the .999 cop req duration instead

[XuHuaiyu]

What problem does this PR solve?

Issue Number: Ref #59815

Problem Summary:
The TiDB -> Distsql -> Coprocessor Seconds 999 panel uses the tidb_tikvclient_cop_duration_seconds_bucket metric to gather data, but this metric is redundant. We can use tidb_tikvclient_request_seconds_bucket to obtain the same data. Therefore, tidb_tikvclient_cop_duration_seconds_bucket can be removed to save storage space.

client-go PR tikv/client-go#1602

What changed and how does it work?

Before:

After:

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @XuHuaiyu. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.9161%. Comparing base (57315c9) to head (925aa9e).
Report is 48 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59845        +/-   ##
================================================
+ Coverage   73.1389%   74.9161%   +1.7772%     
================================================
  Files          1708       1754        +46     
  Lines        471809     479950      +8141     
================================================
+ Hits         345076     359560     +14484     
+ Misses       105518      97778      -7740     
- Partials      21215      22612      +1397     

Flag	Coverage Δ
integration	48.8344% <ø> (?)
unit	72.3533% <ø> (+0.0085%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	62.3042% <ø> (+15.0910%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[zimulala]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-03-03 03:34:29.413480874 +0000 UTC m=+239782.542400618: ☑️ agreed by zimulala.
• 2025-03-13 14:38:05.086143687 +0000 UTC m=+453040.691672614: ☑️ agreed by lance6716.

[tiprow]

@XuHuaiyu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	194c0d5	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

Instructions 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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance6716, tangenta, zimulala

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lance6716,tangenta,zimulala]
• pkg/infoschema/OWNERS [tangenta]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #60390.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #60391.
But this PR has conflicts, please resolve them!

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #60392.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #60393.
But this PR has conflicts, please resolve them!

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #60394.