Failed to acknowledge TcpDiscoveryClientMetricsUpdateMessage

[Calvin KL Wong, CLSA]

Hi,

 

I am getting the error below from my client node.

It couldn’t get an ack for a TcpDiscoveryClientMetricsUpdateMessage it sent out.

 

Can you please let me know the nature of this TcpDiscoveryClientMetricsUpdateMessage message? 

-          The main question is why did this happen?

-          Who is responsible for acknowledging this message?

-          Is ‘id’ my own nodeId?

 

2018-06-25 07:15:37,672 ERROR [tcp-client-disco-sock-writer-#2%blaze_jchx%] org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi - Failed to send message: null

java.io.IOException: Failed to get acknowledge for message: TcpDiscoveryClientMetricsUpdateMessage [super=TcpDiscoveryAbstractMessage [sndNodeId=null, id=77acfc33461-4b6e43a7-4d57-44c4-bcbb-8afba0af7014, verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null, isClient=true]]

        at org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1276) ~[ignite-core-2.3.0-clsa.20180130.59.jar:2.3.0-clsa.20180130.59]

        at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) ~[ignite-core-2.3.0-clsa.20180130.59.jar:2.3.0-clsa.20180130.59]

 

We are using Ignite 2.3.

 

Thanks,

Calvin

 

Calvin KL Wong

Sr. Lead Engineer, Execution Services

D  [phone]  |  M  [phone]  |  T  [phone]

5/F, One Island East, 18 Westlands Road, Island East, Hong Kong

 

 

clsa.com

Insights. Liquidity. Capital.

 

 

A CITIC Securities Company

 

The content of this communication is intended for the recipient and is subject to CLSA Legal and Regulatory Notices.
These can be viewed at https://www.clsa.com/disclaimer.html or sent to you upon request.
Please consider before printing. CLSA is ISO14001 certified and committed to reducing its impact on the environment.

[aealexsandrov]

Hi,

This is a message that provides metrics for other nodes. You can take a look
at it in the source code.

However, looks like your client try to receive the acknowledgment for some
message from some node and there is no answer from this node. Possible that
the required node quit from the cluster or stopping.

For more details, you can set debug logging and set the acknowledgment
timeout:

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.html#setAckTimeout-long-

For more details could you please describe your use case and share the logs?

BR,
Andrei




--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/