Arijit created CASSANDRA-14215:
----------------------------------
Summary: Cassandra does not seem to be respecting max hint window
Key: CASSANDRA-14215
URL: https://issues.apache.org/jira/browse/CASSANDRA-14215
Project: Cassandra
Issue Type: Bug
Components: Hints, Streaming and Messaging
Reporter: Arijit
On Cassandra 3.0.9, it was observed that Cassandra continues to write hints
even though a node remains down (and does not come up) for longer than the
default 3 hour window.
After doing "nodetool setlogginglevel org.apache.cassandra TRACE", we see the
following log line in cassandra (debug) logs:
StorageProxy.java:2625 - Adding hints for [/10.0.100.84]
One possible code path seems to be:
cas -> commitPaxos(proposal, consistencyForCommit, true); -> submitHint (in
StorageProxy.java)
The "true" parameter above explicitly states that a hint should be recorded and
ignores the time window calculation performed by the shouldHint method invoked
in other code paths. Is there a reason for this behavior?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
