[
https://issues.apache.org/jira/browse/IGNITE-29107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-29107:
-----------------------------------
Description: Add `ActiveComputeTasksPerConnection` metric to the
client.connector registry (available via JMX/read API) - the maximum number of
active compute tasks across all active thin-client connections. (was: 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.)
> Add ClientConnector metric for current peak of running comute 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
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add `ActiveComputeTasksPerConnection` metric to the client.connector
> registry (available via JMX/read API) - the maximum number of active compute
> tasks across all active thin-client connections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
