[
https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297707#comment-15297707
]
stone commented on CASSANDRA-11569:
-----------------------------------
a new question about cross datacenter latency.
I add more workload than the cross datacenter network bandwidth,so the value of
crossNodeLatency would be very large,
about 10s,and I think there will be more tcp messages stay in the source
datacenter,so the memory will be increase as the time goes by.and
the source datacenter node will OOM.
but in fact,I have not met this problem.I got info like this.
"log":"INFO 04:22:11 MUTATION messages were dropped in last 5000 ms: 49 for
internal timeout and 0 for cross node timeout. Mean internal dropped latency:
465181 ms and Mean cross-node dropped
so I guess that when the latency is too long ,the mutations tcp messages will
not be sended.is that right?
> Track message latency across DCs
> --------------------------------
>
> Key: CASSANDRA-11569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11569
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability
> Reporter: Chris Lohfink
> Assignee: Chris Lohfink
> Priority: Minor
> Attachments: CASSANDRA-11569.patch, CASSANDRA-11569v2.txt,
> nodeLatency.PNG
>
>
> Since we have the timestamp a message is created and when arrives, we can get
> an approximate time it took relatively easy and would remove necessity for
> more complex hacks to determine latency between DCs.
> Although is not going to be very meaningful when ntp is not setup, it is
> pretty common to have NTP setup and even with clock drift nothing is really
> hurt except the metric becoming whacky.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
