[
https://issues.apache.org/jira/browse/IGNITE-20839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin reassigned IGNITE-20839:
------------------------------------------
Assignee: Mikhail Pochatkin
> Compute jobs queue
> ------------------
>
> Key: IGNITE-20839
> URL: https://issues.apache.org/jira/browse/IGNITE-20839
> Project: Ignite
> Issue Type: Improvement
> Components: compute
> Reporter: Mikhail Pochatkin
> Assignee: Mikhail Pochatkin
> Priority: Major
> Labels: ignite-3
>
> A job queue is a structure showing upcoming Compute jobs for each node. From
> this definition it follows that each node will have its own queue and no
> mechanism for sharing information about queues is yet expected.
>
> The standard queue interface is almost enough for us, with the exception of
> the priority adding method. When adding jobs to the queue normally, we will
> follow the FIFO strategy, i.e. the default priority value when adding a job
> to the queue is 0.
>
> Priority is an int value between [Int.MIN_VALUE, Int.MAX_VALUE]. Jobs with
> the same priority have a FIFO resolving strategy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
