You can set a queue's max_concurrent_requests in queue.yaml (max-concurrent-requests in queue.xml). You could try adding these tasks to their own queue where max_concurrent_requests is 1.
Nick Verne On Sun, Jun 17, 2012 at 3:58 AM, Mahron <[email protected]> wrote: > Hi, > > I need a way for certain tasks from the queue to not execute in parallel to > avoid contention. I figured out the best way to do that was with a pull > queue and a backend filtering tasks to avoid that. > > I was wondering if it would be possible to add a feature to do such a think > automatically, with tasks having a specific group id, preventing them from > executing in parallel but one after the other. I think it would be a great > feature for avoiding contention issues. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/I7zg4SezX_4J. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
