Are you aware that after an update of the code the cron jobs get a reset of the timer.
Maybe the time before cron gets back after an update is 10 minutes. My cron jobs run hours apart. 2010/3/19 stumpy <[email protected]>: > To provide a little more information: > > I have a cron that is set up to run every one minute to initialise a > cache refresh. However over the past few nights during the time of > 4pm-11pm GMT the logs show there to be gaps of 10 minutes or greater > between some invocations. > > > On Mar 18, 11:15 pm, stumpy <[email protected]> wrote: >> Anyone from google care to comment? >> >> I noticed this again tonight and I rely on cron to start my cache >> refresh task. When cron fails to run my data becomes stale and this is >> unacceptable. My understanding was that cron is a reliable service >> with maybe +/- 2 minutes error rate. What level of service should I >> expect from cron? and is it reasonable to kickstart critial processes >> via cron? or is this not recommended? >> >> On Mar 17, 11:39 pm, stumpy <[email protected]> wrote: >> >> > Has anyone else noticed recently that the cron service has became >> > unreliable, often executing 10 minutes late and sometimes skipped >> > entirely for periods of several hours? >> >> > Prehaps an entry should be added to the status page for cron, task >> > queue and other similar services. > > -- > 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. > > -- 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.
