IIRC there is an overhead of about 1MB per table which you have about 5000-10000 => 5GB - 10GB overhead of just having that many tables. To me it looks like that you need to increase the heap size and later potentially work on the data models to have less tables.
Hannu > On 29. Jan 2020, at 15.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 > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
