cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkata Harikrishna Nukala (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14647) Reading cardinality from Statistics.db failed
Date Fri, 01 Mar 2019 15:15:00 GMT


Venkata Harikrishna Nukala commented on CASSANDRA-14647:

[~krummas] Updated the patch. 

> Reading cardinality from Statistics.db failed
> ---------------------------------------------
>                 Key: CASSANDRA-14647
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Observability/Metrics
>         Environment: Clients are doing only writes with Local One, cluster consist of
3 regions with RF3.
> Storage is configured wth jbod/XFS on 10 x 1Tb disks
> IOPS limit for each disk 500 (total 5000 iops)
> Bandwith for each disk 60mb/s (600 total)
> OS is Debian linux.
>            Reporter: Vitali Djatsuk
>            Assignee: Venkata Harikrishna Nukala
>            Priority: Minor
>             Fix For: 3.0.x
>         Attachments: 14647-trunk-1.patch, cassandra_compaction_pending_tasks_7days.png
> There is some issue with sstable metadata which is visible in system.log, the messages
> {noformat}
> WARN  [Thread-6] 2018-07-25 07:12:47,928 - Reading cardinality
from Statistics.db failed for /opt/data/disk5/data/keyspace/table/mc-big-Data.db.{noformat}
> Although there is no such file. 
> The message has appeared after i've changed the compaction strategy from SizeTiered to
Leveled. Compaction strategy has been changed region by region (total 3 regions) and it has
coincided with the double client write traffic increase.
>  I have tried to run nodetool scrub to rebuilt the sstable, but that does not fix the
> So very hard to define the steps to reproduce, probably it will be:
>  # run stress tool with write traffic
>  # under load change compaction strategy from SireTiered to Leveled for the bunch of
>  # add more write traffic
> Reading the code it is said that if this metadata is broken, then "estimating the keys
will be done using index summary". 
>  []

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message