The debug output is from the failure detector in the gossip module. Code can be found here https://github.com/apache/cassandra/blob/8b3a60b9a7dbefeecc06bace617279612ec7092d/src/java/org/apache/cassandra/gms/FailureDetector.java#L450-L474 .
The debug logging above is reporting around an acknowledgement latency between 2 to 3 seconds for each gossip message sent by the node to the respective IP addresses. This is above the expected 2 sec threshold as stated in MAX_INTERVAL_IN_NANO. As Varun pointed out your cluster is probably under too much load. The pressure on your cluster might also be causing the read repairs you reported in your earlier email. Regards, Akhil On Wed, May 31, 2017 at 7:21 AM, Varun Gupta <var...@uber.com> wrote: > Can you please check Cassandra Stats, if cluster is under too much load. > This is the symptom, not the root cause. > > On Tue, May 30, 2017 at 2:33 AM, Abhishek Kumar Maheshwari < > abhishek.maheshw...@timesinternet.in> wrote: > >> Hi All, >> >> >> >> Please let me know why this debug log is coming: >> >> >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:31,496 FailureDetector.java:456 - >> Ignoring interval time of 2000686406 for /XXX.XX.XXX.204 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:34,497 FailureDetector.java:456 - >> Ignoring interval time of 2349724693 <(234)%20972-4693> for >> /XXX.XX.XXX.207 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:34,497 FailureDetector.java:456 - >> Ignoring interval time of 2000655389 for /XXX.XX.XXX.206 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:34,497 FailureDetector.java:456 - >> Ignoring interval time of 2000721304 for /XXX.XX.XXX.201 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:34,497 FailureDetector.java:456 - >> Ignoring interval time of 2000770809 for /XXX.XX.XXX.202 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:34,497 FailureDetector.java:456 - >> Ignoring interval time of 2000825217 for /XXX.XX.XXX.209 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:35,449 FailureDetector.java:456 - >> Ignoring interval time of 2953167747 for /XXX.XX.XXX.205 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:37,497 FailureDetector.java:456 - >> Ignoring interval time of 2047662469 <(204)%20766-2469> for >> /XXX.XX.XXX.205 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:37,497 FailureDetector.java:456 - >> Ignoring interval time of 2000717144 for /XXX.XX.XXX.207 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:37,497 FailureDetector.java:456 - >> Ignoring interval time of 2000780785 for /XXX.XX.XXX.201 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:38,497 FailureDetector.java:456 - >> Ignoring interval time of 2000113606 for /XXX.XX.XXX.209 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:39,121 FailureDetector.java:456 - >> Ignoring interval time of 2334491585 for /XXX.XX.XXX.204 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:39,497 FailureDetector.java:456 - >> Ignoring interval time of 2000209788 for /XXX.XX.XXX.207 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:39,497 FailureDetector.java:456 - >> Ignoring interval time of 2000226568 for /XXX.XX.XXX.208 >> >> DEBUG [GossipStage:1] 2017-05-30 15:01:42,178 FailureDetector.java:456 - >> Ignoring interval time of 2390977968 for /XXX.XX.XXX.204 >> >> >> >> *Thanks & Regards,* >> *Abhishek Kumar Maheshwari* >> *+91- 9999805591 <+91%2099998%2005591> (Mobile)* >> >> Times Internet Ltd. | A Times of India Group Company >> >> FC - 6, Sector 16A, Film City, Noida, U.P. 201301 | INDIA >> >> *P** Please do not print this email unless it is absolutely necessary. >> Spread environmental awareness.* >> >> >> > >
