[
https://issues.apache.org/jira/browse/IGNITE-22349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kukushkin updated IGNITE-22349:
--------------------------------------
Description:
We want Apache Ignite to support [priority
ordering|https://ignite.apache.org/docs/latest/distributed-computing/job-scheduling#priority-ordering]
of Ignite.NET compute jobs on the same node.
h3. Analysis
{{PriorityQueueCollisionSpi}} does priority ordering. The problem is the
{{PriorityQueueCollisionSpi}} expects the user to provide job priorities
via the {{ComputeTaskSession}}'s "{{grid.task.priority}}" attribute and the
{{ComputeTaskSession}} is not available in Ignite.NET.
It looks like the requirement is to add an injectable {{ComputeTaskSession}} in
Ignite.NET exposing the {{SetAttributes}} operation similar to what the
{{ComputeTaskSession}} does in Java.
was:
We want Apache Ignite to support [priority
ordering](https://ignite.apache.org/docs/latest/distributed-computing/job-scheduling#priority-ordering)
of Ignite.NET compute jobs on the same node.
h3. Analysis
{{PriorityQueueCollisionSpi}} does priority ordering. The problem is the
{{PriorityQueueCollisionSpi}} expects the user to provide job priorities
via the {{ComputeTaskSession}}'s "{{grid.task.priority}}" attribute and the
{{ComputeTaskSession}} is not available in Ignite.NET.
It looks like the requirement is to add an injectable {{ComputeTaskSession}} in
Ignite.NET exposing the {{SetAttributes}} operation similar to what the
{{ComputeTaskSession}} does in Java.
> Ignite.NET support for priority ordering of Compute jobs
> --------------------------------------------------------
>
> Key: IGNITE-22349
> URL: https://issues.apache.org/jira/browse/IGNITE-22349
> Project: Ignite
> Issue Type: Improvement
> Components: .NET, compute, platforms
> Affects Versions: 2.16
> Reporter: Alexey Kukushkin
> Assignee: Alexey Kukushkin
> Priority: Major
> Labels: .net, compute, platforms
>
> We want Apache Ignite to support [priority
> ordering|https://ignite.apache.org/docs/latest/distributed-computing/job-scheduling#priority-ordering]
> of Ignite.NET compute jobs on the same node.
> h3. Analysis
> {{PriorityQueueCollisionSpi}} does priority ordering. The problem is the
> {{PriorityQueueCollisionSpi}} expects the user to provide job priorities
> via the {{ComputeTaskSession}}'s "{{grid.task.priority}}" attribute and the
> {{ComputeTaskSession}} is not available in Ignite.NET.
> It looks like the requirement is to add an injectable {{ComputeTaskSession}}
> in Ignite.NET exposing the {{SetAttributes}} operation similar to what the
> {{ComputeTaskSession}} does in Java.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)