Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Connection Timeout Issue #6604

Closed
ankit21491 opened this issue Dec 22, 2022 · 0 comments
Closed

Connection Timeout Issue #6604

ankit21491 opened this issue Dec 22, 2022 · 0 comments

Comments

@ankit21491
Copy link

Hi All,

I am using Fluent Bit version 2.0.5 running as a daemon set in Kubernetes clusters. The K8s env I am having at my organisation are K8s clusters at edge and around 100 clusters are there. I am getting the issue with the Fluent-Bit forwarding the logs to NewRelic, for few of the clusters that the FluentBit pod got stuck in connection timeout and not able to get any logs beyond that.
When checked we are getting the FluentBit uptime metrices which is being scrapped through prometheus. Since FluentBit image is a distroless one so even Liveness Probe can't be set to restart the pod in case if we are not getting the metric.

Connection timeout I can understand could be a network issue but pod getting stuck to timed out and not restarting or dropping the connection is an issue. Also I have checked the PR #3192 which says the issue of connection timeout is fixed in v1.7.0 and ownwards but still issue persists.

Please suggest any resolution for the same.

image

@fluent fluent locked and limited conversation to collaborators Jan 2, 2023
@lecaros lecaros converted this issue into discussion #6637 Jan 2, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant