[
https://issues.apache.org/jira/browse/CASSANDRA-11388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204877#comment-15204877
]
Paulo Motta edited comment on CASSANDRA-11388 at 3/21/16 7:35 PM:
------------------------------------------------------------------
On CASSANDRA-10241 we downgraded all DEBUG level logging to TRACE but probably
forgot to reduce this specific statement. Now that debug.log is being shipped
by default this might be a bit verbose/scary so we should maybe decrease the
level to TRACE or log only if happened above a certain threshold in the last
period.
was (Author: pauloricardomg):
On CASSANDRA-10241 we downgraded all DEBUG level logging to TRACE but probably
forgot to reduce this specific statement. Now that debug.log is being shipped
by default this might be a bit verbose/scary so we should maybe decrease the
level to TRACE.
> 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)
