Skip to main content
NetApp Knowledge Base

What does Message Latency under Cassandra Reference

Last Updated:

Applies to



This attribute reports the duration that each message must wait until it is fully executed.

Whenever a message is sent from one node to another, it attaches a timestamp to it along with some versioning information. The first thing the receiving system will do is compare that timestamp to "now". This is what drives the metric. It will then look at the datacenter the source is from to determine which metrics to increment and by how much.

The metric records incoming latency from all things using the message service. The message service is used for read/writes but is also used for streaming and gossip.

This would also be related to deletes and the EC rebalance.

All metadata needs to be updated with where the new location of data will be during a move of erasure coded data.

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.