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

High CPU / Memory usage using kubernetes_events plugin #8138

Closed
mkatana-silkycoders opened this issue Nov 6, 2023 · 5 comments
Closed

High CPU / Memory usage using kubernetes_events plugin #8138

mkatana-silkycoders opened this issue Nov 6, 2023 · 5 comments

Comments

@mkatana-silkycoders
Copy link

mkatana-silkycoders commented Nov 6, 2023

Tested Fluent-bit Version:

  • 2.1.8
  • 2.1.10 (latest)

Number of namespaces: ~400

First problem

High cpu usage when using plugin kubernetes_events, on left without plugin on right with plugin.

CPU Stats
image

Memory
image

Basic example:

    [INPUT]
        name                          kubernetes_events
        tag                           k8s_events
        kube_url                      https://kubernetes.default.svc:443

    [OUTPUT]
        Name                          kafka
        Match                         k8s_events
        Brokers                       kafka:9093
        Topics                        events
        Workers                       3
        rdkafka.compression.codec     gzip
        rdkafka.request.required.acks 1

Second problem

#1

When i set interval_nsec to default from doc events are colleceted and high CPU / Memory usage...

interval_nsec                 500000000

#2

When i set interval_nsec to 10000000000, events are not collected and theres no high CPU / Memory usage

interval_nsec                 10000000000

#3

Wrong default value its not 5 seconds, its 0.5s ?!

image

image

#4

When i use: interval_sec 60 events are not collected and no CPU / Memory high usage

@mkatana-silkycoders
Copy link
Author

mkatana-silkycoders commented Nov 6, 2023

@pwhelan @edsiper @leonardo-albertovich @fujimotos @koleini

probably releated to #7557

@pwhelan
Copy link
Contributor

pwhelan commented Nov 7, 2023

It might be better to reconsider increasing the interval to 5 seconds as the default. Initially it was even lower, @edsiper?

@pwhelan pwhelan reopened this Nov 7, 2023
Copy link
Contributor

github-actions bot commented Feb 7, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

@github-actions github-actions bot added the Stale label Feb 7, 2024
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2024
@mkatana-silkycoders
Copy link
Author

reopen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants