[
https://issues.apache.org/jira/browse/IGNITE-29107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-29107:
-----------------------------------
Description:
Add two metrics to the client.connector registry (available via JMX/read API):
# ActiveComputeTasksPerConnection — the maximum number of active compute tasks
across all active thin-client connections of the node at poll time (a gauge;
the value can decrease, and it is 0 when there are no connections)
# MaxComputeTasksPerConnection — the configured
MaxActiveComputeTasksPerConnection limit.
# When the limit is 0 (compute disabled), both metrics are equal to 0.
was:
h2. Description
Currently there is no way to determine whether a data region is persistent or
in-memory from its metrics.
We can add a boolean metric {{PersistenceEnabled}} to each data region, which
will return {{true}} for persistent regions and {{false}} for in-memory
regions, determined once at startup.
h2. Acceptance Criteria
* Every data region exposes the {{PersistenceEnabled}} metric after node
startup.
* Value is {{true}} for persistent regions and {{false}} for in-memory regions.
* Value always matches the region's persistence configuration (except for
client nodes).
* Metric is visible in standard monitoring (e.g., JMX) alongside other data
region metrics.
* Existing data region metrics behave unchanged.
> Add ClientConnetor metrics for current and max active tasks
> -----------------------------------------------------------
>
> Key: IGNITE-29107
> URL: https://issues.apache.org/jira/browse/IGNITE-29107
> Project: Ignite
> Issue Type: Task
> Reporter: Ilya Shishkov
> Assignee: Ilya Shishkov
> Priority: Minor
> Fix For: 2.19
>
>
> Add two metrics to the client.connector registry (available via JMX/read
> API):
> # ActiveComputeTasksPerConnection — the maximum number of active compute
> tasks across all active thin-client connections of the node at poll time (a
> gauge; the value can decrease, and it is 0 when there are no connections)
> # MaxComputeTasksPerConnection — the configured
> MaxActiveComputeTasksPerConnection limit.
> # When the limit is 0 (compute disabled), both metrics are equal to 0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
