Hi Kesava,
It's just a guess, I assume that the cron entry in question was
supposed to run on "dynamic" backend instance.
If that's the case, the cron execution can be a single point of
failure, because the cron never retries.
I'd suggest directing all the cron execution to FE, and for the task
you want to run on backend instances, put a task on a queue associated
to the backend instance. That way, you can mitigate the risk that the
cron execution ends up with an error.
Additionally, you can make the initial cron call redundant in a safe
way if you use named tasks.
hope it helps!
-- Takashi
> --
> 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/-/Zl579CSFHe4J.
> To post to this group, send email to
google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
>
google-appengi...@googlegroups.com.
> For more options, visit this group at
>
http://groups.google.com/group/google-appengine?hl=en.
--
Takashi Matsuo | Developer Advocate |
tma...@google.com