> I have a message processing job which listens to the message queue. When > my > flask application is initiated, I try to create 3 workers (or whatever > called in that sense) of them working through @spoolraw. > > What is the best way to ensure a background task is running and ensure it > is not killed by uwsgi? Is the spooler worker right way to do this? > > I see them die without any failure. There is no way I could find out to > check if they are working. So I started to think there is something wrong > with my design. > > All I want to do is to run a new listener if someone dies and ensure three > listeners working. My code is not strictly plain so that I cannot share. > But if needed, I will try to demonstrate a similar scenario. > > > > If needed details: I use puka to connect to rabbitmq. Puka has a wait for > a > message <http://majek.github.io/puka/puka.html#puka.Client.basic_consume> > method, > so I cannot tell a hypothetical monitoring application that "I am alive" > in > a timely manner. Because, it does not respond until a message arrives. > Which I am not sure how much time it will take. Next message may arrive in > a minute or in a month, or not at all. > > Appreciate ideas. > >
If understand correctly you need 3 processes that wait on the puka queue, right ? If yes, mules are the thing you are searching for. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
