Connecting fluentd timeout causes openstack project startup problems

Open
#154 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes, python
Domain
backend, observability-sre

Research direction

No file, test, or entry point is identified in the issue. Reproduce the Kubernetes case where the Fluentd pod dies while its service remains available, then trace the Python logger's connection and timeout behavior; done means the OpenStack application no longer hangs indefinitely when Fluentd is unavailable.

Written by the indexing model from the issue text.

Description

I encountered one such bug.I use k8s to deploy my application,and send the log to fluentd.However, when fluentd's pod dies, fluentd's service is still normal.At this time, my openstack application will not start up and will keep trying to connect fluentd's service.
Is there anyone who can help me?

Dominant language
Python
Stars
457
Forks
138
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluent/fluent-logger-python

All issues in fluent/fluent-logger-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.