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

Why not just set Config.Metadata.Full to false? #2849

Open
wy92 opened this issue Apr 2, 2024 · 1 comment
Open

Why not just set Config.Metadata.Full to false? #2849

wy92 opened this issue Apr 2, 2024 · 1 comment
Labels
stale Issues and pull requests without any recent activity

Comments

@wy92
Copy link

wy92 commented Apr 2, 2024

Description

since every kafka client operation(produce/consume/...) will refresh metadata when the operation was failed, and retry the operation when client get metadata success. why not just set Config.Metadata.Full to false as default? this will reduce a lots of network traffic/ broker's cpu pressure/client's memory pressure when kafka cluster saved a large number of topics.

Additional context

Copy link

github-actions bot commented Jul 1, 2024

Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the main branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.

@github-actions github-actions bot added the stale Issues and pull requests without any recent activity label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues and pull requests without any recent activity
Projects
None yet
Development

No branches or pull requests

1 participant