log: Add upgrade progress information to the logs

[ystaticy]

What problem does this PR solve?

Issue Number: ref #58255

Problem Summary:

What changed and how does it work?

Print progress information during the upgrade process:

[2024/12/13 18:13:31.057 +08:00] [INFO] [bootstrap.go:1565] ["upgrade in progress, a version has just been completed or be skipped."] [keyspaceName=ks1] [old-start-version=182] [in-progress-version=upgradeToVer210] [latest-version=239]

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.

Upgrading TiDB from a lower version to a higher version, with upgrade version update. The following logs can be observed during the process:

[2024/12/13 18:13:31.057 +08:00] [INFO] [bootstrap.go:1565] ["upgrade in progress, a version has just been completed or be skipped."] [keyspaceName=ks1] [old-start-version=182] [in-progress-version=upgradeToVer210] [latest-version=239]

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.

Add upgrade progress information to the logs

[tiprow]

Hi @ystaticy. 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

Attention: Patch coverage is 60.86957% with 9 lines in your changes missing coverage. Please review.

Project coverage is 73.8558%. Comparing base (aa19d3f) to head (2787daf).
Report is 26 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58246        +/-   ##
================================================
+ Coverage   73.1646%   73.8558%   +0.6911%     
================================================
  Files          1680       1681         +1     
  Lines        462997     466620      +3623     
================================================
+ Hits         338750     344626      +5876     
+ Misses       103434     101254      -2180     
+ Partials      20813      20740        -73     

Flag	Coverage Δ
integration	43.3359% <0.0000%> (?)
unit	72.5602% <60.8695%> (+0.2652%)	⬆️

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

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

[zimulala]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-16 03:15:18.523114788 +0000 UTC m=+840308.611917316: ☑️ agreed by zimulala.
• 2024-12-16 03:30:30.038896817 +0000 UTC m=+841220.127699356: ☑️ agreed by djshow832.

[yudongusa]

@ystaticy any test to cover this change?

[ystaticy]

@ystaticy any test to cover this change?

@yudongusa I added a UT case,PTAL~

[bb7133]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bb7133, benmeadowcroft, djshow832, tiancaiamao, 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 [bb7133,djshow832,tiancaiamao,zimulala]
• pkg/session/OWNERS [benmeadowcroft]

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