-
Notifications
You must be signed in to change notification settings - Fork 138
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
using fluent-logger-python with eventlet #183
Comments
I don't know about eventlet, but I have been using it with gevent in production for about 4 years now with no problems. |
I saw fluent-logger uses |
The question is how does eventlet monkey-patch the |
I understand, but I am still interested why last_error is stored and how can I take advantage of it. Because I am afraid this may not be easy to solve for eventlet, so if last_error is not used, I am thinking to fork the repo and maintaining a custom version... |
The reason for a thread local last error is because the same sender is global, can be shared by multiple threads as it's stateless, except for last error. Furthermore, the same behavior in AsyncSender allows the last error to be attributed to the invoking thread. It's not the best design but it's been there for a long time. Judging by eventlet/eventlet#741, it has been confirmed to be an eventlet bug.
|
Hello,
I saw a surprising memory usage growth (see this issue). But when I remove
monkey_patch
looks like memory usage back to normal. Does fluent-logger-python compatible with eventlet?The text was updated successfully, but these errors were encountered: