> I run a http router with: > > ./uwsgi -M --http :8888 --http-subscription-server :2626 > > and nodes with: > > ./uwsgi --subscribe-to 127.0.0.1:2626:localhost:8888 \ > -s 127.0.0.1:0 -w werkzeug.testapp:test_app > > if I kill the node with CTRL-C and start it again, in the router I can > see: > > [uwsgi-subscription for pid 13413] new pool: localhost:8888 > [uwsgi-subscription for pid 13413] localhost:8888 => new node: > 127.0.0.1:42485 > [uWSGI http pid 13413] localhost:8888 => marking 127.0.0.1:42485 as failed > [uwsgi-subscription for pid 13413] localhost:8888 => new node: > 127.0.0.1:46465 > > > then every other request I do with "curl http://localhost:8888/ -i" > is successful but every other errors out with: > > curl: (52) Empty reply from server > > this happens with 1.2 and the latest tip (2290:305e6cdce19f) >
the http-router has only just started to get fastrouter features (the two codebases should merge soon). If you plan to use the http router directly as the frontend/load-balancer you need to wait some week, otherwise you may want to try something like: http-router/nginx/apache/cherokee -> fastrouter -> uWSGIs instances For a full uWSGI setup: uwsgi --http :8888 --http-to :4040 --fastrouter :4040 --fastrouter-subscription-server :2626 -M -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
