Hi, See the attached. Note the abrupt stop..thats where I updated the hash. I have 4 servers running one gevent loop per core. So..its clear that the code does what its supposed to do...but I guess there is a runaway worker. I dont know how to explain it.
On Sun, Dec 30, 2012 at 7:56 PM, Roberto De Ioris <[email protected]> wrote: > > > Hi, > > I am using the gevent loop. > > > > > > I am updating a dictionary every 60 seconds. Its a global dict that all > > workers should read. Content should stop being served if a key is not > > present. It does work but I see that a tiny about of content is still > > being sever. If a do a global restart then no content is severed but > > prefer not to do that. Below is how I reload and I use target='workers'. > > Is there anything I can do to stop the leakage? > > > > from uwsgidecorators import * > > @rbtimer(60,target='workers') > > def load_redis(signum): > > loadRedisDict() > > _______________________________________________ > > uWSGI mailing list > > [email protected] > > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > > > You mean that after all of the workers have updated their dictionary (are > you sure all of them have updated it ?) it looks like some greenlet is not > reading it and continue serving requests ? > > Does this behaviour ends after a bit ? (check for 60 seconds) > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
<<attachment: render_leakage.png>>
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
