You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Joel Knighton (JIRA)" <ji...@apache.org> on 2016/03/22 21:38:25 UTC

[jira] [Resolved] (CASSANDRA-11388) FailureDetector.java:456 - Ignoring interval time of

     [ https://issues.apache.org/jira/browse/CASSANDRA-11388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Knighton resolved CASSANDRA-11388.
---------------------------------------
    Resolution: Not A Problem

This message alone is not cause for concern. 

In the future, the bug tracker is for reports of issues you've identified or concrete improvements you'd like to propose.

The Cassandra user mailing list or Cassandra IRC can help you determinate if something is likely an issue if you aren't sure.

> 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)