Hi, >> Alexey, why do you think it will be useful?
I need to execute some tasks periodically on cluster. I think it is a common task. I could aggregate data once a day, I could generate reports and so on... Nodes can fail, cluster could be restarted. And with new persistence feature distributed scheduling that survives cluster restart could be implemented. >>A similar topic was raised and discussed some time ago: >>http://apache-ignite-developers.2346864.n4.nabble. com/Tasks-Scheduling-and-Chaining-td14293.html I read that topic it is a bit different from my point of view. I'm talking only about periodical or one-time planned jobs on cluster that will be executed with some guaranties. But we also can take into account that use-case. On Fri, Jun 30, 2017 at 5:53 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Alexey, why do you think it will be useful? > > On Thu, Jun 29, 2017 at 12:22 PM, Alexey Kuznetsov <akuznet...@apache.org> > wrote: > > > Hi, All! > > > > I would like to start discussion about distributed scheduling. > > > > So, Ignite already has a module "ignite-schedule" that provide API for > > LOCAL scheduling on node. > > And if node failed - schedule will be lost. > > > > So, it will be very useful feature to have distributed scheduling. > > > > Lets discuss how it could be implemented. > > > > I see two options: > > 1) Extend "ignite-schedule" module to have API for distributed > > scheduling. > > 2) Extend compute API with methods that will allow scheduling of tasks > on > > cluster. > > 3) Implement both of 1) and 2) ? > > > > Any ideas and thought are welcomed! > > > > -- > > Alexey Kuznetsov > > > -- Alexey Kuznetsov
