feat: support tidb in data source, sql tool, and execute sql tool

[Icemap]

This PR supports TiDB in:

1. sources - tidb: As a data source;
2. tools - tidb - tidbsql: As a prepared SQL running tool;
3. tools - tidb - tidbexecutesql: As an arbitrary SQL running tool (for development purposes).

And its corresponding docs.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[Icemap]

CLA was signed now. How can I make the CLA checking bot recheck the status?

[kurtisvg]

@Icemap there's a little button in the check details that says "click here to update CLA check". I've triggered it for this PR and looks like it's green

[Icemap]

Thanks @kurtisvg, if you find any issues or have some suggestions during the code review, please let me know. I'll fix it ASAP.

[kurtisvg]

Thanks @Icemap! We've had a lot of interest in the repo over the last two days, which is making us run behind. Please give us a few days and we'll get back to you!

[duwenxin99]

/gcbrun

[github-actions]

🔎 Preview at https://googleapis.github.io/genai-toolbox/previews/PR-829/

[Yuan325]

Hi @Icemap ! Sorry for the late response. I left some comments on this PR. While you make the changes, I'll also start setting up TiDB vm in our integration test.

Please let me know if you require more clarification on any of the feedbacks! :) Thank you again for contributing!!

[c4pt0r]

Thanks @Icemap! We've had a lot of interest in the repo over the last two days, which is making us run behind. Please give us a few days and we'll get back to you!

any updates on this? really appreciate it

[Icemap]

Great, @Yuan325. Thanks for the feedback. I'll apply those suggestions ASAP.

[Icemap]

Hi @Yuan325 . I've applied all your suggestions. You are such a great reviewer! Thanks for your collaboration. If I missed something, please feel free to leave more suggestions. Great work!

[Icemap]

That's cool! @Yuan325 It's a great move, and I'll add more features to enrich these tools later.

[Yuan325]

@Icemap Hi! We found that the TiDB's log has been taking a big space from the VM and often hit disk full state.

I've tried to add the following config in my topo.yaml:

server_configs:
  tidb:
    log.file.max-days: 1
    log.file.max-backups: 1

monitoring_servers:
  - host: 10.128.0.2
    storage_retention: 1d

However, my ~/data/tidb-deploy/prometheus-9090/data/tidb-data still consist of datas generated from 6 days ago. I'm wondering if that's not the right configuration to set prometheus storage retention?

Thank you!

[Icemap]

Got it. Let me loop in our o11y engineers in this PR.

[Icemap]

Here is a solution that you can use to delete the extra data immediately, which is restarting Prometheus with an extra parameter. @Yuan325 https://ask.pingcap.com/t/how-to-adjust-the-data-retention-period-for-monitoring-servers/9439
And then, we can check why the TiUP's config didn't sync up to Prometheus.

[Yuan325]

@Icemap Got it. Yeah, when I check ps -ef|grep prometheus, it shows --storage.tsdb.retention=30d, which is different from what I set in topo.yaml (2d).

My prometheus service only start with tiup, how do I restarting just that with the extra parameter (tiup cluster restart <cluster-name> -R prometheus won't allow to add prometheus specific flags)? I'm assuming we should not be restarting prometheus with the systemctl. If you have the command line that'll be great.