kafka(ticdc): sarama do not retry if produce message failed to prevent out of order

[3AceShowHand]

What problem does this PR solve?

Issue Number: close #11935

What is changed and how it works?

• config.Net.MaxOpenRequest is set to 1
• config.Producer.Retry.Max is set to 0, to disable the internal retry mechanism

The root cause of the out-of-order message problem comes from the sarama internal bug, cannot be easily fixed, this is a workaround solution, by set the retry.max to 0, to disable the retry.

Check List

Tests

• Unit test
• Integration test

This is tested by an internal E2E test, which inject network partition between the random cdc node and random kafka server. Before this PR, the test case cannot be passed, and we found out-of-order message by reading consumer log, after this PR it can be passed, and no out-of-order message.

Questions

Will it cause performance regression or break compatibility?

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

Release note

fix the sarama retry caused out-of-order message by set retry count to 0 as a workaround

[3AceShowHand]

/retest

[3AceShowHand]

/retest

[3AceShowHand]

/retest

[3AceShowHand]

/retest

[3AceShowHand]

/retest

[3AceShowHand]

/retest

[3AceShowHand]

/retest

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-31 06:42:40.487588653 +0000 UTC m=+419095.843593192: ☑️ agreed by wk989898.
• 2024-12-31 07:13:30.961607392 +0000 UTC m=+420946.317611963: ☑️ agreed by asddongmen.

[3AceShowHand]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asddongmen, hongyunyan, wk989898

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 [asddongmen,hongyunyan,wk989898]

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

[3AceShowHand]

/retest

[3AceShowHand]

/cherry-pick release-8.1
/cherry-pick release-7.5

[3AceShowHand]

/cherry-pick release-8.5

[ti-chi-bot]

@3AceShowHand: new pull request created to branch release-7.5: #11960.

In response to this:

/cherry-pick release-8.1
/cherry-pick release-7.5

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 ti-community-infra/tichi repository.

[ti-chi-bot]

@3AceShowHand: new pull request created to branch release-8.5: #11961.

In response to this:

/cherry-pick release-8.5

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 ti-community-infra/tichi repository.

[ti-chi-bot]

@3AceShowHand: new pull request created to branch release-8.1: #11962.

In response to this:

/cherry-pick release-8.1
/cherry-pick release-7.5

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 ti-community-infra/tichi repository.

[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-dm-integration-test	f1d8b2e	link	true	/test dm-integration-test
pull-cdc-integration-pulsar-test	f1d8b2e	link	true	/test cdc-integration-pulsar-test

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.