Skip to content

Conversation

D3Hunter
Copy link
Contributor

What problem does this PR solve?

Issue Number: close #58480

Problem Summary:

What changed and how does it work?

Check List

Tests

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

tiup playground; add sleep(5 seconds) on domain reload, and then start a tidb with this PR. run create table

before

[2024/12/24 18:28:04.889 +08:00] [INFO] [syncer.go:403] ["syncer check all versions, all nodes are not synced"] [category=ddl] ["ddl job id"=111] [ver=55]
[2024/12/24 18:28:05.891 +08:00] [INFO] [syncer.go:403] ["syncer check all versions, all nodes are not synced"] [category=ddl] ["ddl job id"=111] [ver=55]

after

[2024/12/24 18:45:50.058 +08:00] [INFO] [syncer.go:398] ["syncer check all versions, someone is not synced"] [category=ddl] [info="instance ip 192.168.206.89, port 5000, id 8d02f9b2-bfe1-4292-a1ef-5c1ef86eebf8"] ["ddl job id"=117] [ver=58]
  • 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

@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Dec 24, 2024
Copy link

tiprow bot commented Dec 24, 2024

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

Copy link

codecov bot commented Dec 24, 2024

Codecov Report

Attention: Patch coverage is 28.57143% with 5 lines in your changes missing coverage. Please review.

Project coverage is 75.1026%. Comparing base (457dcc6) to head (be92c7b).
Report is 78 commits behind head on master.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #58511        +/-   ##
================================================
+ Coverage   73.5697%   75.1026%   +1.5328%     
================================================
  Files          1681       1726        +45     
  Lines        464249     473865      +9616     
================================================
+ Hits         341547     355885     +14338     
+ Misses       101876      95696      -6180     
- Partials      20826      22284      +1458     
Flag Coverage Δ
integration 49.2511% <0.0000%> (?)
unit 72.4919% <28.5714%> (+0.1547%) ⬆️

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

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

@D3Hunter
Copy link
Contributor Author

/retest

Copy link

tiprow bot commented Dec 24, 2024

@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Dec 25, 2024
Copy link

ti-chi-bot bot commented Dec 25, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance6716, wjhuang2016

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:

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 ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Dec 25, 2024
Copy link

ti-chi-bot bot commented Dec 25, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-12-25 05:38:32.585190851 +0000 UTC m=+1626502.673993393: ☑️ agreed by lance6716.
  • 2024-12-25 08:08:41.297109901 +0000 UTC m=+1635511.385912449: ☑️ agreed by wjhuang2016.

@ti-chi-bot ti-chi-bot bot merged commit 623191c into pingcap:master Dec 25, 2024
27 checks passed
@D3Hunter D3Hunter deleted the fix-sync-version-log branch December 25, 2024 12:12
@ti-chi-bot ti-chi-bot bot added the needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. label Jan 7, 2025
@ti-chi-bot
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

when only some node hasn't sync, DDL owner always print 'syncer check all versions, all nodes are not synced'
4 participants