Val and Michael , Very good point!
Any idea how it could be implemented? Actually I need distributed scheduling. On Thu, Jun 22, 2017 at 5:37 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > I think Michael brought up a very good point. Current ignite-scheduler > module schedules jobs only locally which is not very useful in distributed > system. I don't think I've ever seen it used and I don't think it makes > sense to spend time on it if we just replace one dependency with another. > However, if we switch to Quartz in order to enhance functionality and > introduce distributed scheduling - that can add value. > > -Val > > On Wed, Jun 21, 2017 at 3:21 PM, Michael André Pearce < > michael.andre.pea...@me.com> wrote: > > > If taking the quartz route, it be great if ignite could expose a > > distributed ignite job store, so you could setup and use quartz in a > > distributed way, in a similar way to terracotta or hazelcasts quartz > > jobstores. > > > > > > Sent from my iPhone > > > > > On 21 Jun 2017, at 15:43, Alexey Kuznetsov <akuznet...@gridgain.com> > > wrote: > > > > > > Hi! > > > > > > Good point, I will take a look. > > > > > >> On Wed, Jun 21, 2017 at 5:42 PM, 李玉珏 <sahala...@163.com> wrote: > > >> > > >> Hi， > > >> > > >> > > >> There is also an alternative that the community can consider using the > > >> scheduling functionality in the spring-context module, for the > following > > >> reasons: > > >> 1.quartz is a very heavy framework, and most functions we don't need; > > >> 2., we already have spring dependencies in our project without > > introducing > > >> new dependencies; > > >> 3.spring is also Apache 2.0 license; > > >> 4.spring's scheduler supports standard CRON, and cron4j does not > support > > >> standard CRON; > > >> 5.spring's code quality is very good, maintainability is good, and the > > >> quality of quartz code is not very good. > > >> On 06/21/2017 13:26，Alexey Kuznetsov<akuznet...@apache.org> wrote： > > >> Hi! > > >> > > >> 1) Cron4J is very old: > > >> Latest Cron4j 2.2.5 released: *28-Dec-2011 * > > >> Latest Quarz 2.3.0 released: *20-Apr-2017* > > >> > > >> 2) Not very friendly license: > > >> CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE > > >> Quartz is freely usable, licensed under the *Apache 2.0* license. > > >> > > >> So, if we replace Cron4J with Quartz we can move *ignite-schedule* > > module > > >> from lgpl profile to main distribution. > > >> > > >> Any objections? > > >> > > >> If no, I will create JIRA issue and implement this change. > > >> > > >> -- > > >> Alexey Kuznetsov > > >> > > > > > > > > > > > > -- > > > Alexey Kuznetsov > > > GridGain Systems > > > www.gridgain.com > > > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
