Does uWSGI Spooler maintain task ordering with multiple workers?
0 reputation · 02 Aug 2020, 08:14 UTC
Task Persistence and Ordering in uWSGI Spooler
The uWSGI Spooler allows for background task offloading by utilizing a directory-based queue system. While tasks are persisted to disk to survive reloads, maintaining a strict First-In-First-Out (FIFO) execution sequence is critical for certain integration workflows.
The spooler-ordered configuration option is intended to enforce this sequence. However, there is uncertainty regarding how this behavior scales when spooler-processes is set to a value greater than one, as multiple workers may attempt to consume tasks from the same directory simultaneously.
Which configuration settings or constraints are required to ensure that spooler-ordered remains effective when utilizing multiple spooler workers? Does the presence of multiple workers inherently invalidate FIFO guarantees regardless of the ordering flag?
uwsgi