mathieulongtin

How about something like this: ```./av setup $INVENTORY_GIT_URI``` The inventory contains the `config` file. The aviary.sh doesn't. Setup does: 1. clone inventory in temp file 2. read the config 3....

It does, as long as the different disque instances can talk to each other. But you can't control which instance get a replication, so there would be scenarios where there...

I kind of like the BURY and KICK command of Beanstalkd for that. When a job is problematic, you bury it, it stays in the queue but is never distributed....

A few alternatives: - For each tag, put a list of queues in a configuration system, for example, a file or a Redis instance - Put the initial message in...

No, you would need to submit the job to a different queue for each service. It would be nice for disque to support this more natively like NSQ or Kafka....

Correct.

Have M1.x create Mz.x1 before its done. Envoyé de mon iPad > Le 16 mars 2016 à 05:47, Amit Prakash Ambasta [email protected] a écrit : > > Message Groups in...

It seems Mz depends on M1. When C1 picks up M1, after it's done, it creates Mz. Disque doesn't support job dependencies at this point. On Wed, Mar 16, 2016...

Your worker should do this: * `GETJOB` * Do stuff * If job is successfully accomplished: `ACKJOB $JID` If you don't call `ACKJOB` or `FASTACK`, disque assumes the worker failed,...

Try this instead `$ redis-cli -h eu1-queue-3 -p 7712 addjob testqueue testjob 1000 replicate 3`