consumer: fix pulsar consumer stuck after broker restart

[wk989898]

What problem does this PR solve?

Issue Number: close #4834

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`.

[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 charlescheung96 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

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

[coderabbitai]

Warning

Rate limit exceeded

@wk989898 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 58 minutes and 33 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 58 minutes and 33 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0911ec7e-ff0d-4d7c-a168-3104ce2f86f5

📥 Commits

Reviewing files that changed from the base of the PR and between 94cd0a7 and e0cd51c.

📒 Files selected for processing (1)

• cmd/pulsar-consumer/consumer.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch wk989898-patch-4

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ti-chi-bot]

@wk989898: The following test 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-error-log-review	e0cd51c	link	true	/test pull-error-log-review

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.

[gemini-code-assist]

Code Review

This pull request refactors the message consumption logic in cmd/pulsar-consumer/consumer.go by replacing the channel-based selection with a direct call to pulsarConsumer.Receive(ctx). Feedback suggests that this change causes context cancellations to be logged as errors rather than informational messages, which could be misleading during graceful shutdowns. It is recommended to check for context cancellation specifically to maintain the previous logging behavior.

[gemini-code-assist]

The current implementation logs an error when the context is cancelled (e.g., during a graceful shutdown), as pulsarConsumer.Receive(ctx) returns context.Canceled. This is misleading because context cancellation is an expected way to stop the consumer. It's better to check for this specific error and log it at the Info level, consistent with the previous logic.

if err != nil {
			if errors.Cause(err) == context.Canceled {
				log.Info("terminating: context cancelled")
				return errors.Trace(err)
			}
			log.Error("Receive message error", zap.Error(err))
			return errors.Trace(err)
		}