Priority on affinityCalls

[chewie <an...@gmail.com>]

Hello and thank you for this project. It's awesome!

I'm adapting an older DB-centric application to use Ignite in order to be
more scalable and I'm trying to make my affinityCalls work in a prioritized
order but can't really work it out. There seems to be a bit of documentation
on Job Scheduling but that seems to be for the ComputeTaskSplitAdapter. So
the question is: can I add a priority to an IgniteCallable and make that
callable be executed on the server node in a prioritized order?
Thanks in advance.

/Anders



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Priority on affinityCalls

[Stanislav Lukyanov <st...@gmail.com>]

I personally feel that this should be handled on higher level.
In my view, Ignite Compute subsystem is about simple delivery of a job
to a remote server. It has failover and all, but to really use that you have to
go for ComputeTaskSplitAdapter or similar things, and they’re hard to get right.

I’d rather see some sort of distributed job scheduler as a higher level subsystem,
e.g. built as an Ignite Service.

Or, one could say that all you need is a distributed priority queue.
We already have a regular FIFO queue as an Ignite Data Structure.
Why not add another one?

In any case, I think you should ask on dev@ignite.apache.org
what other people think.
And the best way to get this feature is to contribute it! :)

Stan

From: chewie
Sent: 16 октября 2018 г. 11:31
To: user@ignite.apache.org
Subject: RE: Priority on affinityCalls

Hi Stan,

Thanks for your quick response! Could something like prioritized callables
be considered in a future version? Currently in my project a bunch of client
nodes send all kinds of affinityCalls to the server nodes and a real-time
interaction task and a slow moving batch job probably shouldn't be executed
with the same urgency. I just feel I wouldn't be the only one gaining from
such a feature.

/Anders



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Priority on affinityCalls

[chewie <an...@gmail.com>]

Hi Stan,

Thanks for your quick response! Could something like prioritized callables
be considered in a future version? Currently in my project a bunch of client
nodes send all kinds of affinityCalls to the server nodes and a real-time
interaction task and a slow moving batch job probably shouldn't be executed
with the same urgency. I just feel I wouldn't be the only one gaining from
such a feature.

/Anders



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Priority on affinityCalls

[Stanislav Lukyanov <st...@gmail.com>]

Hi,

Nope, there is no priority queue for affinity calls.
ComputeTaskSplitAdapter seems to be the best way to handle this.

As an alternative, you could do something similar with a cluster singleton service:
submit tasks to it, sort by priority, and send them to the servers as affinityRun.

Not sure which approach is easier to implement.

Stan

From: chewie
Sent: 15 октября 2018 г. 18:05
To: user@ignite.apache.org
Subject: Priority on affinityCalls

Hello and thank you for this project. It's awesome!

I'm adapting an older DB-centric application to use Ignite in order to be
more scalable and I'm trying to make my affinityCalls work in a prioritized
order but can't really work it out. There seems to be a bit of documentation
on Job Scheduling but that seems to be for the ComputeTaskSplitAdapter. So
the question is: can I add a priority to an IgniteCallable and make that
callable be executed on the server node in a prioritized order?
Thanks in advance.

/Anders



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/