Hi Behroz, It looks like the number of tables is the problem, with 5,000 - 10,000 tables, that is way above the recommendations.
Take a look here: https://docs.datastax.com/en/dse-planning/doc/planning/planningAntiPatterns.html#planningAntiPatterns__AntiPatTooManyTables <https://docs.datastax.com/en/dse-planning/doc/planning/planningAntiPatterns.html#planningAntiPatterns__AntiPatTooManyTables> This suggests that 5-10GB of heap is going to be taken up just with the table information ( 1MB per table ) Thanks Paul > On 29 Jan 2020, at 14:50, Behroz Sikander <bsikan...@apache.org> wrote: > >>> Some environment details like Cassandra version, amount of physical RAM, > JVM configs (heap and others), and any other non-default cassandra.yaaml > configs would help. The amount of data, number of keyspaces & tables, > since you mention "clients", would also be helpful for people to suggest > tuning improvements. > > We are more or less using the default properties. > Here are some more details > > - Total nodes in the cluster - 9 > - Disk for each node is 2 TB > - Number of keyspaces - 1000 > - Each keyspace has 5-10 tables > - We observed this problem on a c4.4xlarge (AWS EC2) instance having 30GB RAM > with 8GB heap > - We observed the same problem on a c4.8xlarge having 60GB RAM with 12GB heap > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org >
