Vladimir Steshin created IGNITE-26179:
-----------------------------------------

             Summary: Metrics of TCPCommunication connection pool.
                 Key: IGNITE-26179
                 URL: https://issues.apache.org/jira/browse/IGNITE-26179
             Project: Ignite
          Issue Type: Improvement
            Reporter: Vladimir Steshin
            Assignee: Vladimir Steshin


Among the settings of _TcpCommunication_ we have parameters like 
{_}usePairedConnections, connectionsPerNode{_}, {_}messageQueueLimit{_}.

These settings can improve throughput, reduce latency and limit unsent data 
memory consumption . But we have no indicator hinting that the current settings 
of the pool aren't enough.

We've met user experience where a user had to use {_}usePairedConnections{_}. 
But to find it out where, an external analysis tool (like JRF) was required.

To provide information of connection pool utilization we may expose its metric. 
Metrics are often provided by vasious common connection pools.

The metrics might be:
 * Pool size
 * Number of currently open connections
 * Number of active connections
 * Average connection idle time
 * Average connection lifetime
 * Number of closed connections

And also
 * Number of unsent messages to each node



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to