Skip to content

Don't raise errors for the events larger than max-message-bytes #1405

Description

@flowbehappy

Currently, TiCDC use max-message-bytes for two usages:

  1. To be the max batch size during batching multiple events into one message before sending to Kafka
  2. Stop message larger than max-message-bytes being sent to Kafka. CDC raises an error if a message is larger, e.g. Single message is too large for avro.

While, in fact, those two usages should be set separately, instead of relying on one single setting. Because a user could send a single event with larger size.

And since there is already a message.max.bytes in the Kafka topic setting or Kafka Broker setting, we don't need to limit the message size on TiCDC any more. So I suggest we simply remove the second usage of max-message-bytes from TiCDC.

Metadata

Metadata

Assignees

Labels

type/enhancementThe issue or PR belongs to an enhancement.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions