Re: reported bloom filter FP ratio

>                Read Count: 68844 [snip] > why reported bloom filter FP ratio is not counted like this 10/68844.0 > 0.00014525594096798558 Because the read count is total amount of reads to the CF, while the bloom filter is per sstable. The number of individual reads to sstables will be high

reported bloom filter FP ratio

I have following CF Read Count: 68844 Read Latency: 9.942 ms. Write Count: 209712 Write Latency: 0.297 ms. Pending Tasks: 0 Bloom Filter False Postives: 10 Bloom Filter False Ratio: 0.0

R: Re: Counters and Top 10

Hi all, I've red all your messages concerning the top 10 ... any solution is possibile but I still did not find the best one. Using a composite Column Name as suggested would be smart cause it brings to a sorted row where I can have my top-10 in any moment but it can slow down all the platform

Nodetool move failure, no data partitions determined

I was moving around some nodes in my cluster but when I get one node there appears an error: "Error during move: The data partitions for node [IP] have not been determined" How to solve this problem? -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.c

Re: Counters and Top 10

With Composite Column Name, you can even have column composed of sore (int) and userid (uuid or whatever). Empty column value to avoid repeating user UUID. 2011/12/22 R. Verlangen : > I would suggest you to create a CF with a single row (or multiple for > historical data) with a date as key (utf8