As well, please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send an empty email to [email protected] and follow simple instructions in the reply.
Kind regards, Alex. On Thu, Aug 24, 2017 at 5:41 PM, afedotov <[email protected]> wrote: > Hi, > > 1. For scheduling jobs, you can take a look at the cron based scheduler > <https://apacheignite.readme.io/docs/cron-based-scheduling>. > It provides facilities for scheduling jobs locally, but you can run any > distributed task from that scheduled task. > 2. Information about all the jobs associated with a task you can obtain > from the ComputeTaskFuture returned from the > ignite.compute().executeAsync call as follows > fut.getTaskSession().getJobSiblings() > 3. Pausing and resuming is not supported out of the box, but you could > implement it using, for example, distributed task session > <https://apacheignite.readme.io/docs/compute-tasks#section-distributed-task-session> > or distributed data structures > <https://apacheignite.readme.io/docs/data-structures> > 4. There is no schema for persisting jobs as it is done for Quartz instead > you need to maintain the scheduled futures in some way. > > > > Kind regards, > Alex. > > On Thu, Aug 24, 2017 at 3:50 PM, chandrika [via Apache Ignite Users] <[hidden > email] <http:///user/SendEmail.jtp?type=node&node=16397&i=0>> wrote: > >> Hello All, >> >> We have a requirement of parallel processing/executing of tasks across >> nodes to improve the performance of the application, hence are using >> Apache Ignite. So far we have found Apache Ignite very useful. >> >> Also would like to use ignite-schedule extensively for all the below >> points in cluster: >> >> 1. scheduling the job >> 2. to fetch all the tasks or the jobs associated with the task >> 3. to pause / resume / delete / reschedule the job >> 4. also is there a schema of DB for persisting the jobs scheduled already >> 5. also can we schedule a job with cron for a particular time and date. >> >> in short need a replacement for Quartz. >> >> thanks and regards, >> chandrika >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> http://apache-ignite-users.70518.x6.nabble.com/fetching-all- >> the-tasks-already-scheduled-and-to-know-the-status-of-the- >> task-tp16393.html >> To start a new topic under Apache Ignite Users, email [hidden email] >> <http:///user/SendEmail.jtp?type=node&node=16397&i=1> >> To unsubscribe from Apache Ignite Users, click here. >> NAML >> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> > > > ------------------------------ > View this message in context: Re: fetching all the tasks already > scheduled and to know the status of the task > <http://apache-ignite-users.70518.x6.nabble.com/fetching-all-the-tasks-already-scheduled-and-to-know-the-status-of-the-task-tp16393p16397.html> > Sent from the Apache Ignite Users mailing list archive > <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com. >
