Thank you for your reply. I’ll increase memTable_flush_writes and report back if it helps.
Is there any formula that we can use to arrive at correct number of memTable_flush_writers ? or the exercise would windup be like “try and error” taking much time to arrive at some number that may not be optimal. Thank you again. From: Anuj Wadehra [mailto:anujw_2...@yahoo.co.in] Sent: Thursday, July 20, 2017 12:17 PM To: ZAIDI, ASAD A <az1...@att.com>; user@cassandra.apache.org Subject: Re: MUTATION messages were dropped in last 5000 ms for cross node timeout Hi Asad, You can do following things: 1.Increase memtable_flush_writers especially if you have a write heavy load. 2.Make sure there are no big gc pauses on your nodes. If yes, go for heap tuning. Please let us know whether above measures fixed your problem or not. Thanks Anuj Sent from Yahoo Mail on Android<https://urldefense.proofpoint.com/v2/url?u=https-3A__overview.mail.yahoo.com_mobile_-3F.src-3DAndroid&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FsmDztdsVuIKml8IDhdHdg&m=wu-cVspapPKFg21Ul4vRDSw9hpc-s7H1OxPMTPTEApE&s=YCtcGLTbnUV3ZWX_ZFNGe-DCoXPuokN0NCCwS_ahD2I&e=> On Thu, 20 Jul 2017 at 20:57, ZAIDI, ASAD A <az1...@att.com<mailto:az1...@att.com>> wrote: Hello Folks – I’m using apache-cassandra 2.2.8. I see many messages like below in my system.log file. In Cassandra.yaml file [ cross_node_timeout: true] is set and NTP server is also running correcting clock drift on 16node cluster. I do not see pending or blocked HintedHandoff in tpstats output though there are bunch of MUTATIONS dropped observed. <start timeout message > INFO [ScheduledTasks:1] 2017-07-20 08:02:52,511 MessagingService.java:946 - MUTATION messages were dropped in last 5000 ms: 822 for internal timeout and 2152 for cross node timeout <end timeout message > I’m seeking help here if you please let me know what I need to check in order to address these cross node timeouts. Thank you, Asad
