[
https://issues.apache.org/jira/browse/IGNITE-21199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-21199:
---------------------------------------
Description:
We have service tasks such as GC, and we anticipate more, which consume
resources shared with user tasks, such as queries. These tasks should not
monopolize resources when a node is engaged in user queries but should utilize
all resources during idle times.
We need to develop a common mechanism to manage resource allocation between
service tasks and user tasks, ensuring this component is reusable across
different service task-creating components.
The idea is to assign a weight to each user/system operation. The weight can be
the approx number of dirty pages, produced by an operation. Before attempting
an operation, a corresponding weight must be "reserved" in the total weight
pool (configurable by a user)
was:
We have service tasks such as GC, and we anticipate more, which consume
resources shared with user tasks, such as queries. These tasks should not
monopolize resources when a node is engaged in user queries but should utilize
all resources during idle times.
We need to develop a common mechanism to manage resource allocation between
service tasks and user tasks, ensuring this component is reusable across
different service task-creating components.
> Introduce a mechanism to manage and schedule Ignite services tasks
> ------------------------------------------------------------------
>
> Key: IGNITE-21199
> URL: https://issues.apache.org/jira/browse/IGNITE-21199
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Gagarkin
> Priority: Major
> Labels: ignite-3
>
> We have service tasks such as GC, and we anticipate more, which consume
> resources shared with user tasks, such as queries. These tasks should not
> monopolize resources when a node is engaged in user queries but should
> utilize all resources during idle times.
> We need to develop a common mechanism to manage resource allocation between
> service tasks and user tasks, ensuring this component is reusable across
> different service task-creating components.
> The idea is to assign a weight to each user/system operation. The weight can
> be the approx number of dirty pages, produced by an operation. Before
> attempting an operation, a corresponding weight must be "reserved" in the
> total weight pool (configurable by a user)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
