Measures reported by IgniteTcpComTest

Ignite TCP Communication SPI is the default communication SPI which uses TCP/IP protocol and JAVA NIO to communicate with other nodes.At startup, this SPI tries to start listening to local port specified in config. If local port is occupied, then SPI will automatically increment the port number until it can successfully bind for listening. Defined configuration parameters controls maximum number of ports that SPI will try before it fails. Port range comes very handy when starting multiple grid nodes on the same machine or even in the same VM. In this case all nodes can be brought up without a single change in configuration.

Since TCP Communication SPI enables the communication between the ports it is one of the most important enablers of the cluster to work. That's the reason it is absolutely important to monitor this SPI so that even if there is a minor glitch in its operation administrators should know it first and take remediation action before it affects teh system performance.

This test monitors the TCP communication SPI and gathers key metrics around messages sent and received between nodes, and looking at these metrics administrators can understand the current status of SPI.

Outputs of the test: One set of results for each Apache Ignite Server

The measures made by this test are as follows: