Please create an issue on the issue tracker for this feature request. On Thursday, May 17, 2012 6:15:38 PM UTC+10, Ian Marshall wrote: > > Thank you > --------- > You're welcome. > > > In option 1: Do you mean using *etaMillis of **TaskOptions *using to > specify the execute time? > ----------------------------------------------------------------------------------------------- > > > Yes. > > > We can trigger a TaskInit by cron and create 48 tasks in queue(every > 30 minutes) to avoid chain task. > ----------------------------------------------------------------------------------------------------- > > > Good idea: I didn't think of that. > > > I just wish a simple syntax to support such requirement > ------------------------------------------------------- > Me too. > > > On May 17, 3:13 am, Larry <[email protected]> wrote: > > Hi Lan, > > Thank you. > > In option 1: > > Do you mean using *etaMillis of **TaskOptions *using to specify the > > execute time? > > This could be a solution. We can trigger a TaskInit by cron and create > 48 > > tasks in queue(every 30 minutes) > > to avoid chain task. > > > > In option 2: > > This is my first thought about cron.xml . I just wish a simple > syntax > > to support such requirement. > > If I change the schedule from 30 minutes to 2 minutes, the cron.xml will > be > > 1800 entries. > > > > Ian Marshall於 2012年5月16日星期三UTC+8下午5時15分11秒寫道： > > > > > > > > > > > > > > > > > > > > > Your syntax problem may lie within your "schedule" tag (mix of month > > > and every, and unwanted final comma): > > > > > <schedule>1,15, of month every 2 hours</schedule> > > > > > Your "description" tag and posting text do not match the every 2 hours > > > in your "schedule" tag. Assuming that you want to run every 30 > > > minutes... > > > > > Option 1: try > > > > > <schedule>1,15 of month 00:00</schedule> > > > > > and at the end of your scheduled task enqueue a task to execute 30 > > > minutes later, if this would be within the same day. > > > > > Option 2: try > > > > > <schedule>1,15 of month 00:00</schedule> > > > <schedule>1,15 of month 00:30</schedule> > > > <schedule>1,15 of month 01:00</schedule> > > > <schedule>1,15 of month 01:30</schedule> > > > ... > > > <schedule>1,15 of month 23:30</schedule> > > > > > This is more robust than chaining enqueued tasks kicked off by a > > > scheduled task, but would be more cumbersome to code, since you will > > > need a cron entry for each schedule. > > > > > Is this any help? > > > > > On May 15, 12:20 pm, Larry <[email protected]> wrote: > > > > Hello All, > > > > Is it possible to execute my job as following: > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > <cronentries> > > > > <cron> > > > > <url>/mytask</url> > > > > <description>Execute my task, every 30 minutes of first and15th > of > > > > month </description> > > > > <schedule>1,15, of month every 2 hours</schedule> > > > > <timezone>America/New_York</timezone> > > > > </cron> > > > > </cronentries> > > > > > > This syntax is wrong and fail to deploy to GAE. > > > > I tested another solution. Execute mytask every 30 minutes. Execute > the > > > > real task only the date is 1 and 15. > > > > I check the dashboard. The Frontend Instance Hours increase > > > dramatically. > > > > > > Any thoughts? > > > > Larry
-- 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/-/QMCRPOibj2wJ. 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.
