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.

Sign up for GitHub

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

Jump to bottom

Avoid FD spike after retrying KafkaAdminClient #32

Merged
merged 1 commit into from
Aug 8, 2024
Merged

Avoid FD spike after retrying KafkaAdminClient #32

merged 1 commit into from
Aug 8, 2024

Commits on Aug 8, 2024

  1. Avoid FD spike after retrying KafkaAdminClient 

    A caller might call kafka.KafkaAdminClient repeatedly and handle
kafka.errors.NoBrokersAvailable if the broker is not available.

However, each retry will cause 3 extra FD being used. Depends on how
long the caller wait before retry, the FD usage can reach 300~700 before
Python garbage collector collecting those FD.

This commit close those FD early.
    @orange-kao
    orange-kao committed Aug 8, 2024
    Configuration menu
    Copy the full SHA
    dfe42d0 View commit details
    Browse the repository at this point in the history