Hi Thomas, 1. Yes, they are stored in the system collection _jobs. System collections are usually replicated to at least one other node. 2. The behavior of a failed job can be defined when creating a job (see docs <https://docs.arangodb.com/3.1/Manual/Foxx/Scripts.html#adding-a-job-to-a-queue>). Failed jobs will not impact the queue. 3. Jobs aren't purged automatically, you have to delete them manually (see docs <https://docs.arangodb.com/3.1/Manual/Foxx/Scripts.html#deleting-a-job-from-the-queue>). This can also be done with a periodic job.
Best Mark Am Dienstag, 25. April 2017 04:05:39 UTC+2 schrieb Thomas Weiss: > > Hi everyone, > > Still working on my social network project (I swear I will blog about how > it uses Arango once things get less busy!), I'm now considering using Foxx > queues to asynchronously denormalize the users' feed. Some questions: > 1. I guess that queues are stored in system collections, so by default > they don't get replicated to other nodes? > 2. What happens when a job fails? Does the queue continue to process the > remaining jobs or does it halt? > 3. I've seen that the API can retrieve a list of successful and failed > jobs, does that mean that this list is stored persistently? Is it purged so > it doesn't grow indefinitely? > > Thanks again for your support, > Thomas > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
