e this:
>> > > > 1) via scheduler:
>> > > > Ignite ignite = Ignition.start();
>> > > >
>> > > > ignite.scheduler().schedulel(job, "0 0 * * *"); // This will execute
>> > job
>> > > > every day at 00:00
>> > > >
>> > > > 2) via compute
>> > > >
>> > > > Ignite ignite = Ignition.start();
>> > > >
>> > > > ignite.compute().schedulel(task, "0 0 * * *"); // This will execute
>> > > > compute
>> > > > task every day at 00:00
>> > > >
>> > > > Make sense?
>> > > >
>> > > >
>> > > Yes, it does, but I am failing to see how is this a *distributed*
>> > > scheduling. Are we persisting the scheduler somewhere in the cluster or
>> > is
>> > > it only triggered on the client side?
>> > >
>> >
>>
t; > > wrote:
> > > >
> > > > > Dmitriy,
> > > > >
> > > > > >> Can you provide a simple example of API calls that will make
> this
> > > > > possible?
> > > > > API could be like this:
> > > > > 1) via sched
> > > Ignite ignite = Ignition.start();
> > > >
> > > > ignite.scheduler().schedulel(job, "0 0 * * *"); // This will execute
> > job
> > > > every day at 00:00
> > > >
> > > > 2) via compute
> > > >
> > > > Ignite ignite = Ignition.start();
> > > >
> > > > ignite.compute().schedulel(task, "0 0 * * *"); // This will execute
> > > > compute
> > > > task every day at 00:00
> > > >
> > > > Make sense?
> > > >
> > > >
> > > Yes, it does, but I am failing to see how is this a *distributed*
> > > scheduling. Are we persisting the scheduler somewhere in the cluster or
> > is
> > > it only triggered on the client side?
> > >
> >
>
; > every day at 00:00
> > >
> > > 2) via compute
> > >
> > > Ignite ignite = Ignition.start();
> > >
> > > ignite.compute().schedulel(task, "0 0 * * *"); // This will execute
> > > compute
> > > task every day at 00:00
> > >
> > > Make sense?
> > >
> > >
> > Yes, it does, but I am failing to see how is this a *distributed*
> > scheduling. Are we persisting the scheduler somewhere in the cluster or
> is
> > it only triggered on the client side?
> >
>
e.scheduler().schedulel(job, "0 0 * * *"); // This will execute job
> > every day at 00:00
> >
> > 2) via compute
> >
> > Ignite ignite = Ignition.start();
> >
> > ignite.compute().schedulel(task, "0 0 * * *"); // This will
task every day at 00:00
>
> Make sense?
>
>
Yes, it does, but I am failing to see how is this a *distributed*
scheduling. Are we persisting the scheduler somewhere in the cluster or is
it only triggered on the client side?
; > 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 s
> 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
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"
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&quo
arnate that thread with the inputs from your side.
—
Denis
> On 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-
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.
Le
12 matches
Mail list logo
