Re: Reason for Trace Message Drop

Thanks Eric Stevens for your detailed reply!! I got your points. On Thu, Jun 16, 2016 at 11:49 PM, Eric Stevens wrote: > Are you executing all queries with tracing enabled? If so that introduces > overhead you probably don't want. Most people probably don't see this log >

Re: Reason for Trace Message Drop

Are you executing all queries with tracing enabled? If so that introduces overhead you probably don't want. Most people probably don't see this log very often because it's the exception to query with tracing enabled, and not the rule (it's a diagnostic thing usually turned on only when

Re: Reason for Trace Message Drop

Thanks!! Eric Stevens for your reply. We have following JVM settings :- - *memtable_offheap_space_in_mb: 15360 (*found in casandra.yaml *)* *MAX_HEAP_SIZE="16G" (*found in cassandra-env.sh *)*- And I also

Re: Reason for Trace Message Drop

This is better kept to the User groups. What are your JVM memory settings for Cassandra, and have you seen big GC's in your logs? The reason I ask is because that's a large number of column families, which produces memory pressure, and at first blush that strikes me as a likely cause. On Wed,

Reason for Trace Message Drop

Hi all, Can anyone tell me that what are all possible reasons for below log:- *"INFO [ScheduledTasks:1] 2016-06-14 06:27:39,498 MessagingService.java:929 - _TRACE messages were dropped in last 5000 ms: 928 for internal timeout and 0 for cross node timeout".* I searched online for the same and