-
Notifications
You must be signed in to change notification settings - Fork 57
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
Client not getting updated toggles in flask app when running via gunicorn with "--preload" option #216
Comments
Thanks for raising this, lots of nice details in this report! I believe I know what's happening here but give me a bit of time to double check myself |
Just updating for folks who arrive here because this ended up on Slack. This is a currently limitation in the Python client that this won't work due to the way gunicorn spawns the underlying processes, right now it's best to not use the |
Hi there! I wanted to check if this is on the radar or being looked at? One of our backend services is hosted on GCP Cloud Run and instance load times are important here where we need to have |
Describe the bug
When running unleash with flask/gunicorn, it is not getting updated with latest toggles from unleash server when it is run with option "--preload". More info on preload
gunicorn --chdir app app:app -w 2 --threads 2 -b 0.0.0.0:80 --preload
To Reproduce
I have a branch to demonstrate. using this demo toggle
https://app.unleash-hosted.com/demo/projects/default/features/gunicorn
docker-compose up --build
http://localhost/test_unleash
--preload
option from https://github.com/raymzag/Flask_Docker_App/blob/master/gunicorn.shdocker-compose up --build
again.Expected behavior
Expects the unleash toggles to be refreshed in flask/gunicorn app with --preload option.
Logs
If applicable, add logs or output to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: