cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9793) Log when messages are dropped due to cross_node_timeout
Date Wed, 22 Jul 2015 08:15:04 GMT


Stefania commented on CASSANDRA-9793:

You're quite right a boolean should be enough, resuming development.

> Log when messages are dropped due to cross_node_timeout
> -------------------------------------------------------
>                 Key: CASSANDRA-9793
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Stefania
>             Fix For: 2.1.x, 2.0.x
> When a node has clock skew and cross node timeouts are enabled, there's no indication
that the messages were dropped due to the cross timeout, just that messages were dropped.
 This can errantly lead you down a path of troubleshooting a load shedding situation when
really you just have clock drift on one node.  This is also not simple to troubleshoot, since
you have to determine that this node will answer requests, but other nodes won't answer requests
from it.  If the problem goes away on a reboot (and the machine does one-shot time sync, not
continuous) it becomes even harder to detect because you're left with a weird piece of evidence
such as "it's fine after a reboot, but comes back in about X days every time."
> It would help tremendously if there were a log message indicating how many messages (don't
need them broken down by type) were eagerly dropped due to the cross node timeout.

This message was sent by Atlassian JIRA

View raw message