Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking issue for Kafka handling large message without halting changefeeds #9153

Open
21 of 25 tasks
3AceShowHand opened this issue Jun 8, 2023 · 0 comments
Open
21 of 25 tasks
Assignees
Labels
area/ticdc Issues or PRs related to TiCDC. kafka type/feature Issues about a new feature

Comments

@3AceShowHand
Copy link
Contributor

3AceShowHand commented Jun 8, 2023

Background

Changefeed send messages to the Kafka server, if the message size is larger than the Kafka's configuration max.message.bytes, an error will be reported to the changefeed and it get stuck.

It's unexpected that an occasional large message cause the whole changefeed cannot make progress. So we propose that, if the message size is large than the message limit, only encode the primary key or the not null unique key of the event, and add a new flag to indicate this. The Kafka consumer once receive such an message, they should use the PK / UK to query the upstream TiDB to get the corresponding data.

Development

Docs

  • update the document to describe the open-protocol with large message only handle columns enabled
@3AceShowHand 3AceShowHand self-assigned this Jun 8, 2023
@3AceShowHand 3AceShowHand added area/ticdc Issues or PRs related to TiCDC. type/feature Issues about a new feature kafka labels Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ticdc Issues or PRs related to TiCDC. kafka type/feature Issues about a new feature
Projects
None yet
Development

No branches or pull requests

1 participant