shishkovilja commented on code in PR #13661: URL: https://github.com/apache/ignite/pull/13661#discussion_r4357120071
########## docs/_docs/monitoring-metrics/new-metrics.adoc: ########## @@ -469,6 +466,7 @@ Register name: `client.connector` |AffinityKeyRequestsMisses | long | The number of affinity-aware cache key requests that were sent not to the primary node. |AffinityQueryRequestsHits | long | The number of affinity-aware query requests that were sent to the primary node. |AffinityQueryRequestsMisses | long | The number of affinity-aware query requests that were sent not to the primary node. +|PeakActiveComputeTasksPerConnection | long | Maximum number of active user compute tasks per thin client connection over the configured time interval (90 seconds by default), but not less than the current value. The upper limit is the `ThinClientConfiguration.maxActiveComputeTasksPerConnection` configuration parameter. A task rejected by the limit counts as the limit. Review Comment: > Why `peak`, not `max` Because, `MaxActiveComputeTasksPerConnection` duplicates corresponding configuration property. May be `MaxCurrentActiveComputeTasksPerConnection` ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
