Tasks need to be written so that they are idempotent (ie can be run again at any point without changing the result). I don't know why you task is being run twice, but this is always a possible but unlikely outcome so they need to be able to deal with this possibility.
T On Saturday, May 17, 2014 8:23:56 PM UTC+8, Malleswari Srinivasarao wrote: > > Hi, > May I know the reason for running same process in multiple > instances. I too faced this in my application, but it was not happened at > the time of loading the application instead, it happened while task queue > was serving one request. The same request handled twice with different > instances at approximately same time (milliseconds difference is there). > The task which my task queue processing was, very sensitive information, > because of this happened, it resulted me great loss as duplication > happened. > > Kindly tell me what was the *reason *to run the same request with > two different instances and *how to avoid* this. I can say, it was not > happening all the time, but when it happens, so much duplication of data > occurred in my case. > > One thing I have observed is, one request was running say, > "/tasks/procesInfo" , after sometime, the same process, > "/tasks/procesInfo" was running in different instance and these two are > parallelly running. Please help me. > > Thanks, > Malleswari. > > > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
