Re: nodetool tablestats reporting local read count of 0, incorrectly

On 2017-04-03 12:42 (-0700), Voytek Jarnot wrote: > Continuing to grasp at straws... > > Is it possible that indexing is modifying the read path such that the > tablestats/tablehistograms output is no longer trustworthy? I notice more > realistic "local read count"

Re: nodetool tablestats reporting local read count of 0, incorrectly

Continuing to grasp at straws... Is it possible that indexing is modifying the read path such that the tablestats/tablehistograms output is no longer trustworthy? I notice more realistic "local read count" numbers on tables which do not utilize SASI. Would greatly appreciate any thoughts,

Re: nodetool tablestats reporting local read count of 0, incorrectly

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

nodetool tablestats reporting local read count of 0, incorrectly

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