[DNM] debug debezium integration test slow failed

[3AceShowHand]

What problem does this PR solve?

Issue Number: close #xxx

What is changed and how it works?

Check List

Tests

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

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

[gemini-code-assist]

Summary of Changes

Hello @3AceShowHand, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces additional logging within the Kafka sink's DDL event handling mechanism. The primary purpose of these changes is to aid in debugging performance or timing-related issues, particularly those encountered during Debezium integration tests. By logging the DDL event's tidbFinishedAt timestamp and the duration since that time, the PR aims to provide deeper insights into the processing lifecycle of DDL events. The [DNM] tag signifies that this PR is likely a diagnostic or work-in-progress branch not intended for immediate merging.

Highlights

• Enhanced DDL Event Logging: Added new log fields to the sendDDLEvent function in downstreamadapter/sink/kafka/sink.go to provide more detailed timing information for DDL events.
• Debugging Focus: The changes introduce logging of tidbFinishedAt (derived from the commit timestamp) and the duration since that time, specifically aimed at debugging slow or failing Debezium integration tests, as indicated by the [DNM] prefix in the PR title.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds debug logging to the Kafka sink for DDL events to help diagnose a slow integration test. The changes calculate the duration since the DDL was committed in TiDB and add it to the log. While this PR is marked as 'Do Not Merge' and is for debugging, I've provided a suggestion to improve the new logging statement for better performance and consistency. My feedback recommends using strongly-typed zap fields instead of zap.Any and aligning the log field key for the DDL query with existing logs in the file.

[3AceShowHand]

/test all

[3AceShowHand]

/test all

[3AceShowHand]

/test pull-cdc-kafka-integration-heavy

[ti-chi-bot]

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

Test name	Commit	Details	Required	Rerun command
pull-cdc-mysql-integration-heavy	94c78c4	link	true	/test pull-cdc-mysql-integration-heavy
pull-cdc-kafka-integration-heavy	94c78c4	link	true	/test pull-cdc-kafka-integration-heavy

Full PR test history. Your PR dashboard.

Details

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]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign flowbehappy for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• OWNERS
• pkg/config/OWNERS

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