nodetool tablehistograms tsg_ae/logs_by_user will give you an idea about the estimate of the partition size. It is recommended that the partition size is not over 100MB
Large partitions are also creating heap pressure during compactions, which will issue warnings in the logs (look for "large partition"). Thanks, Fay On Wed, Jun 14, 2017 at 1:13 PM, Thakrar, Jayesh < jthak...@conversantmedia.com> wrote: > We are on Cassandra 2.2.5 and I am constantly seeing warning messages > about large partitions in system.log even though our setting for partition > warning threshold is set to 4096 (MB). > > > > WARN [CompactionExecutor:43180] 2017-06-14 20:02:13,189 > BigTableWriter.java:184 - Writing large partition > tsg_ae/logs_by_user:114303419784957147 > (17187 bytes) > > WARN [CompactionExecutor:43180] 2017-06-14 20:02:13,190 > BigTableWriter.java:184 - Writing large partition > tsg_ae/logs_by_user:820590487870502244 > (2613 bytes) > > WARN [CompactionExecutor:43180] 2017-06-14 20:02:13,191 > BigTableWriter.java:184 - Writing large partition > tsg_ae/logs_by_user:421586605444858333 > (54923 bytes) > > > > Here's what we have in cassandra.yaml. > > > > # Log a warning when compacting partitions larger than this value > > compaction_large_partition_warning_threshold_mb: 4096 > > > > So wondering if such a warning is normal or is there something wrong in > our configuration or is it a bug? > > > > I have looked at https://issues.apache.org/jira/browse/CASSANDRA-9643. > > > > Any pointers will be greatly appreciated. > > > > Thanks, > > Jayesh > > >
