> Hi all, > > couples of questions for uwsgi spool: > > 1. Does only 1 spool worker allowed to execute at one time?
No, from 1.2 you can have all of the spooler you need (they will run concurrently) on the same spooldir or on different. Ex. --spooler /foobar --spooler /foobar --spooler /foobar2 will run 3 spooler, two pulling from the same dir and one from another. > 2. If a spool task is scheduled to run at a specific time, how do I > prevent > the task from being scheduled multiple times? (e.g. the web client might > submit many times, so a task might be added multiple times.) the "same" task cannot be spooled multiple times (thee is a lock preventing that, even on NFS filesystems), if you mean the same "kind" of task (for example for avoiding task bombing) you have to implement that in your app. > 3. Are there mechanism inside uwsgi that can provide a list of spool tasks > and manage them (display info, delete, rename, re-schedule, enable/disable > etc.) > task files are simple dictionaries encoded in uwsgi format and placed on a dir. You should be able to easily manage them. The uwsgi.spooler_jobs() is a pretty basic enumerator for tasks, but i suggest you to write an external tool. Just remember to take in account only files with the name starting with "uwsgi_spoolfile_on_" -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
