[
https://issues.apache.org/jira/browse/CASSANDRA-11388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205948#comment-15205948
]
Relish Chackochan commented on CASSANDRA-11388:
-----------------------------------------------
Thank You for the reply.
The cluster seems working fine & The similar lines printing frequently on each
nodes.
I am also able to reproduce the same error on another test cluster with 2.2.5v.
Our environment is on VMware ESXi . Without any load on the nodes the message
is coming to the debug.log.
Can i ignore the message or This will cause any issues in future.
DEBUG [OptionalTasks:1] 2016-03-22 07:18:23,275 FileCacheService.java:102 -
Evicting cold readers for
/opt/apache-cassandra-2.2.5/bin/./../data/data/system/local-7ad54392bcdd35a684174e047860b377/la-115-big-Data.db
DEBUG [OptionalTasks:1] 2016-03-22 07:18:23,276 FileCacheService.java:102 -
Evicting cold readers for
/opt/apache-cassandra-2.2.5/bin/./../data/data/system/local-7ad54392bcdd35a684174e047860b377/la-114-big-Data.db
DEBUG [OptionalTasks:1] 2016-03-22 07:18:23,277 FileCacheService.java:102 -
Evicting cold readers for
/opt/apache-cassandra-2.2.5/bin/./../data/data/system/local-7ad54392bcdd35a684174e047860b377/la-113-big-Data.db
DEBUG [GossipStage:1] 2016-03-22 07:18:25,288 FailureDetector.java:456 -
Ignoring interval time of 2001238147 for /10.91.59.68
DEBUG [GossipStage:1] 2016-03-22 07:19:04,021 FailureDetector.java:456 -
Ignoring interval time of 2710894842 for /10.91.59.70
DEBUG [GossipStage:1] 2016-03-22 07:19:11,312 FailureDetector.java:456 -
Ignoring interval time of 2000730678 for /10.91.59.68
DEBUG [GossipStage:1] 2016-03-22 07:19:16,027 FailureDetector.java:456 -
Ignoring interval time of 2710726697 for /10.91.59.70
DEBUG [GossipStage:1] 2016-03-22 07:20:04,268 FailureDetector.java:456 -
Ignoring interval time of 2000329223 for /10.91.59.69
DEBUG [GossipStage:1] 2016-03-22 07:20:11,345 FailureDetector.java:456 -
Ignoring interval time of 2000628247 for /10.91.59.70
DEBUG [GossipStage:1] 2016-03-22 07:20:13,344 FailureDetector.java:456 -
Ignoring interval time of 2001996247 for /10.91.59.68
DEBUG [GossipStage:1] 2016-03-22 07:20:18,061 FailureDetector.java:456 -
Ignoring interval time of 2001020692 for /10.91.59.70
DEBUG [GossipStage:1] 2016-03-22 07:20:33,357 FailureDetector.java:456 -
Ignoring interval time of 2001123684 for /10.91.59.70
DEBUG [GossipStage:1] 2016-03-22 07:20:47,365 FailureDetector.java:456 -
Ignoring interval time of 2000870623 for /10.91.59.70
DEBUG [GossipStage:1] 2016-03-22 07:20:52,368 FailureDetector.java:456 -
Ignoring interval time of 2001912064 for /10.91.59.70
> 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)
