p2p(ticdc): use a larger max receive message size

[overvenus]

What problem does this PR solve?

Issue Number: close #8004

What is changed and how it works?

Use a larger max receive message size to address ResourceExhausted issue.

Check List

Tests

• Unit test
• Manual test
  Setup a changefeed that replicate 72k tables.

Questions

Will it cause performance regression or break compatibility?

No.

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

No.

Release note

Fix an issue that checkpoint can not advance when replicating many tables.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• 3AceShowHand
• amyangfei

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[amyangfei]

Suggested change

	if c.MaxRecvMsgSize <= 0 {
	if c.MaxRecvMsgSize < 0 {

[3AceShowHand]

It looks this 2 case can be switched, check <0 and return the error first, then check if it's 0.

[lance6716]

maybe this can help

tiflow/dm/ctl/common/util.go

Lines 124 to 133 in 73bb333

	switch status.Code(err) {
	case codes.ResourceExhausted:
	matches := re.FindStringSubmatch(err.Error())
	if len(matches) == 3 {
	msgSize, err2 := strconv.Atoi(matches[1])
	if err2 == nil {
	log.L().Info("increase gRPC maximum message size", zap.Int("size", msgSize))
	opts = append(opts, grpc.MaxCallRecvMsgSize(msgSize))
	}
	}

[3AceShowHand]

Suggested change

	MaxRecvMsgSize: 268435456,
	MaxRecvMsgSize: 256 * 1024 * 1024,

[overvenus]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 8b583d9

[overvenus]

/run-engine-integration-test
/run-integration-test

[overvenus]

/run-engine-integration-test

[ti-chi-bot]

@overvenus: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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]

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

[ti-chi-bot]

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