Yeah i am running with paging on, and the output rows returned are not
consistent the max rows i got returned is 7 and i am running with tracing
on and i don't see any tombstones as well. Hpw can i determine if my
partition is large or not ??
i was able to figure out the token from one node and t
Then the partition is too big or has too many sstables that contain data
for that partition so that the query times out. You can run a manual
compaction on that table. That helped me several times.
+ I hope you are not trying to read that parition at once. Please use
paging to query large partitio
Hi Jonathan,
I tried multiple times running the query at consistency all, every time i
run it i getting the same output that co-ordinator is timing out. I can see
it wasn't helping much there were multiple read repair drops. Is there any
other way to get that partition fixed ??
Thanks
Pranay.
O
Query it at consistency ALL and let read repair do its thing.
On Tue, Jun 27, 2017 at 11:48 AM Pranay akula
wrote:
> I have a CF with composite partition key, partition key consists of blob
> and text data types.
> The select query against this particular partition is timing out so to
> debug it
I have a CF with composite partition key, partition key consists of blob
and text data types.
The select query against this particular partition is timing out so to
debug it further i ran nodetool getendpoints i am getting error like below
error: Non-hex characters in 0xbbdcbf21ffb72115599ca915634