I'm experiencing a very tricky bug or "feature" in Taskqueues regarding tasks set with an ETA. Tasks are being executed 1 hour later than expected *in some instances* (inconsistently). I think this behavior started after DST.
In my experience with a handful of scheduled tasks (e.g. development), it works fine. I'm using UTC timestamps in my Tasks set with the "etaMillis()" method in the Taskqueue API. Things execute just when expected. Each night, however, I have thousands of tasks that queue up. This causes multiple AppEngine instances to fire up (and I think this is important--the root cause of the inconsistent behavior). Only during load am I seeing this issue. *Some* tasks--are executing exactly 1 hour behind when they are expected to. My AppEngine region is us-central. Task queues are a wonderful feature of AppEngine. Anyone else experience this with high volumes of scheduled tasks? What's going on? Different app engine instances with different time zone settings? I'm thinking a potential alternative will be to specify countdown instead... maybe this will resolve the issue? -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/16c5395c-a5bd-4272-9a84-ce290af9ec4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
