cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Stevens <migh...@gmail.com>
Subject Re: Reason for Trace Message Drop
Date Wed, 15 Jun 2016 12:45:05 GMT
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, Jun 15, 2016 at 3:23 AM Varun Barala <varunbarala99@gmail.com>
wrote:

> 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 found some reasons like:-
>
> * Disk is not able to keep up with your ingest
> * Resources are not able to support all parallel running tasks
> * If other nodes are down then due to large hint replay
> * Heavy workload
>
> But in this case other kind of messages (mutation, read, write etc)
>  should be dropped by *C** but It doesn't happen.
>
> -----------------------------
> Cluster Specifications
> ------------------------------
> number of nodes = 1
> total number of CF = 2000
>
> -----------------------------
> Machine Specifications
> ------------------------------
> RAM 30 GB
> hard disk SSD
> ubuntu 14.04
>
>
> Thanks in advance!!
>
> Regards,
> Varun Barala
>

Mime
View raw message