>> I've noticed that with recent version of uWSGI, the spooler does not >> treat jobs as it used to. Before, if 10 jobs were in the queue and job >> 1 failed, the spooler would proceed to try job 2 and then job 3, etc. >> But recently, I've noticed that if job1 fails, it will continue to try >> and execute job1 completely ignoring jobs 2-10 until job1 is >> successfully processed. Here is my config: > > > This is pretty strange, as the spooler is not supposed to work in that way. > > How the job is failing ? I mean, it is returning a SPOOL_RETRY or an > Exception ?
I'm noticing this issue when the spooler is failing with an Exception. I have not yet tried a test case with SPOOL_RETRY. > The spooler can only destroy objects created by him, if the code you are > running cannot be freed it will leak. > I suggest you to use > > sys.gettotalrefcount() > > before exiting the function to see if your callable is leaking Sounds good, i'll implement this and get back to you with the results. _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
