Ignite TCP Communication SPI Test

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.

Target of the test : Apache Ignite Server

Agent deploying the test : An internal or external agent

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

Configurable parameters for the test



Test period

How often should the test be executed.


Enter the IP address of the Apache Ignite cluster.


Enter the port number on which JMX connector listens to incoming connections requests.

JMX Remote Port

In this text box, enter the name of a virtual warehouse that needs to be monitored. The JMX connector listens on 8686 by default. If it listens on different port in your environment then specify the same.

JMX User

Specify the credentials of the user who is authorized to use JMX.

JMX Password

Specify the password for the authorized user.

Confirm Password

Confirm the password by retyping it here.

Measurements made by the test



Measurement Unit


Outbound message queue size

Indicates the size of queue for outgoing communication messages for the given node.


The size of queue should be enough to accommodate all the messages waiting to be sent, if the messages are produced faster than they are sent, you might want to increase the queue size.

Messages sent rate

Indicates the number of messages sent per second form the given node.


If the rate is going down over the measurements, it would be the matter of concern.


Messages received rate

Indicates the number of messages received per second on the given node.