Document if Sender is fork-safe.

Open
#60 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by tracing the Python Sender and logging Handler behavior across forked worker processes. Determine whether the socket is cloned or reopened, whether fluentd responses are expected, and whether another sender could read them. Done means the fork-safety behavior and usage implications are documented clearly.

Written by the indexing model from the issue text.

Description

Consider a scenario where:

  • master process attaches fluent Sender or logging Handler
  • master process forks off a bunch of worker processes
  • workers use handler

Will the socket get cloned or reopened?
Does fluent logger expect a response from fluentd?
If it does, can the response be read out by wrong sender process?

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.