Further info - tablehistograms reports zeros for all percentiles for Read Latency; tablestats also reports really low numbers for Bloom filter usage (3-4 KiB, depending on node, whereas I'd expect orders of magnitude more given other - less accessed - tables in this keyspace). This is the most written-to and read-from table in the keyspace, seems to keep up with tracking of writes, but not reads.
Full repair on this table is the only thing I can think of; but that's a guess and doesn't get me any closer to understanding what has happened. On Fri, Mar 31, 2017 at 11:11 PM, Voytek Jarnot <voytek.jar...@gmail.com> wrote: > Cassandra 3.9 > > Have a keyspace with 5 tables, one of which is exhibiting rather poor read > performance. In starting an attempt to get to the bottom of the issues, I > noticed that, when running nodetool tablestats against the keyspace, that > particular table reports "Local read count: 0" on all nodes - which is > incorrect. > > It tallies "Local write count", presumably correctly, as at least it's not > 0. Other tables in the keyspace do not exhibit this behavior, as they > provide non-zero numbers for both read and write values. > > Is this perhaps indicative of a deeper issue with this particular table? > > Thank you. >
