[
https://issues.apache.org/jira/browse/CASSANDRA-11388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204425#comment-15204425
]
Joel Knighton commented on CASSANDRA-11388:
-------------------------------------------
Are you seeing any signs of abnormal behavior in the cluster? Do similar lines
show up in the debug.log to an extreme degree?
These log messages indicate that a node neglected to add an interval time to
the failure detector history for a node because it was above some maximum
threshold. This could be due to local GC or a number of other causes. These log
messages are flagged DEBUG because they may be helpful in tracking down an
issue but don't indicate a problem on their own.
> FailureDetector.java:456 - Ignoring interval time of
> ----------------------------------------------------
>
> Key: CASSANDRA-11388
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11388
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Cassandra 2.2.4
> Reporter: Relish Chackochan
> Priority: Minor
>
> We have Cassandra Cluster of 8 nodes with 2.2.4v using jdk1.8.0_65 ( RHEL 6.5
> 64-bit ) and i am seeing the following error in the Cassandra debug.log file.
> All the nodes are UP and running with
> "nodetool status". NTP is configured on all nodes and Time syncing well.
> DEBUG [GossipStage:1] 2016-03-21 06:45:30,700 FailureDetector.java:456 -
> Ignoring interval time of 3069815316 for /192.168.1.153
> DEBUG [GossipStage:1] 2016-03-21 06:45:30,700 FailureDetector.java:456 -
> Ignoring interval time of 2076119905 for /192.168.1.135
> DEBUG [GossipStage:1] 2016-03-21 06:45:30,700 FailureDetector.java:456 -
> Ignoring interval time of 2683887772 for /192.168.1.151
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
