> > This is better but I would it tell us that worker is loading too much, or > just > that it's unloyal to some undefined reason (since emperor doesn't know > what > worker is doing). > But maybe it could be extended: > 1. worker is going to be started/reloaded > 2. workers sends signal to empreror saying "hey, i'm going to restart now" > 3. emeperor marks worker as starting > 4. if emperor doesn't receive heartbeat in <some time limit in seconds> > since > worker startup than we know it's startup issue and can log proper message > > If we had bidirectional messanging vassla<->emperor, than we could make > emperor more aware of what is going on with vassals. it might be helpfull. > Does it sound like a good idea? Or maybe it's already possible? > uWSGI has so many features I still find myself amazed ;)
Emperor -> vassal, communication is already bi-directional. Every message is 1 byte sent from one of the peers (so we have 256 kind of messages). The protocol is explained here: http://projects.unbit.it/uwsgi/wiki/EmperorProtocol feel free to propose new kind of messages. By the way, i have just realized not all of the users are running under the Emperor (even if they really should :P), so i will try adding the thread-approach, and later we could think about something more advanced using the emperor. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
