pingcap / pingcap/ticdc

The ["topic's `max.message.bytes` less than the `max-message-bytes`..."] warning log should include the Kafka topic name and changefeed name

Open
#4,200 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type/enhancement
Dominant language
Go
Stars
56
Forks
63
Avg merge
2d 20h
Merged PRs (30d)
34

Description

Is your feature request related to a problem?

When you start a changefeed with Kafka sink, and setting max-message-bytes higher than the topic's max.message.bytes, there will be a [WARN] level log like

[2026/02/10 21:31:29.459 +00:00] [WARN] [options.go:611] ["topic's `max.message.bytes` less than the `max-message-bytes`,use topic's `max.message.bytes` to initialize the Kafka producer"] [max.message.bytes=2097164] [max-message-bytes=10485760] [real-max-message-bytes=2097036]

while the topic and changefeed name can be inferred from the surrounding logs, it is harder to find out which log is involved when grepping by keyword alone.

Describe the feature you'd like

Include the topic name & changefeed name to https://github.com/pingcap/ticdc/blob/6ad7b6b65f0da5f34d3df8806b83c68009ff2e3b/pkg/sink/kafka/options.go#L631-L635

Describe alternatives you've considered

No response

Teachability, Documentation, Adoption, Migration Strategy

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in pkg/sink/kafka/options.go around lines 631-635 and inspect the warning emitted when the topic's max.message.bytes is lower than max-message-bytes. Update the warning context so it includes both the Kafka topic name and changefeed name. Done means the warning identifies both names when grepping logs.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kafka
Domain
stream-processing
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.