-
Notifications
You must be signed in to change notification settings - Fork 288
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
TiCDC gets the Kafka metadata too frequently and too aggressive #8959
Closed
2 tasks
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
area/ticdc
Issues or PRs related to TiCDC.
component/sink
Sink component.
kafka
type/enhancement
The issue or PR belongs to an enhancement.
Comments
Rustin170506
added
component/sink
Sink component.
area/ticdc
Issues or PRs related to TiCDC.
kafka
labels
May 15, 2023
Rustin170506
added
the
type/enhancement
The issue or PR belongs to an enhancement.
label
May 25, 2023
/label affects-7.1 |
ti-chi-bot
bot
added
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-6.5
This bug affects the 6.5.x(LTS) versions.
labels
May 26, 2023
This was referenced May 31, 2023
Merged
This was referenced Jun 1, 2023
17 tasks
Rustin170506
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 12, 2023
16 tasks
This was referenced Jun 26, 2023
16 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
area/ticdc
Issues or PRs related to TiCDC.
component/sink
Sink component.
kafka
type/enhancement
The issue or PR belongs to an enhancement.
In TiCDC, we get all topic info with the admin interface:
tiflow/cdc/sink/dmlsink/mq/manager/kafka_manager.go
Line 138 in 1335f98
This would be a problem when you have a lot of topics and changefeeds.
At the same time, the frequency is too high:
tiflow/cdc/sink/dmlsink/mq/manager/kafka_manager.go
Line 87 in 1335f98
So we need to solve the problem to get better performance and avoid affecting the downstream Kafka.
See more at https://asktug.com/t/topic/1005884/2
The text was updated successfully, but these errors were encountered: