CODEWITHSUNDEEP
cassandranodetool
soumyadeep sarkar
soumyadeep sarkar

Reputation: 572

What does different fields of nodetool cfstats mean?

When I am using below command.
nodetool -h localhost -p 7199 cfstats demodb I came up with the following results. I cant get upto any conclusion from the following results. I could not decide whether my two node clustered Cassandra is performing good or need to be tuned. 

 Keyspace: demodb
            Read Count: 81361
            Read Latency: 0.04145315323066334 ms.
            Write Count: 23114
            Write Latency: 0.06758518646707623 ms.
            Pending Tasks: 0
                    Table: schema1
                    SSTable count: 0
                    Space used (live), bytes: 0
                    Space used (total), bytes: 3560
                    SSTable Compression Ratio: 0.0
                    Number of keys (estimate): 0
                    Memtable cell count: 5686
                    Memtable data size, bytes: 3707713
                    Memtable switch count: 5
                    Local read count: 81361
                    Local read latency: 0.000 ms
                    Local write count: 23114
                    Local write latency: 0.000 ms
                    Pending tasks: 0
                    Bloom filter false positives: 0
                    Bloom filter false ratio: 0.00000
                    Bloom filter space used, bytes: 0
                    Compacted partition minimum bytes: 0
                    Compacted partition maximum bytes: 0
                    Compacted partition mean bytes: 0
                    Average live cells per slice (last five minutes): 1.0
                    Average tombstones per slice (last five minutes): 0.0

Upvotes: 1

Views: 3194

Answers (1)

Maxim Zakharenkov
Maxim Zakharenkov

Reputation: 311

As far as i see, I can tell you that your data in the table schema1 is still fully in memory "SSTable count: 0". At this point there is nothing to optimize. The statistics will be more helpful when you have more data and your in-memory state is flushed to disk. It is to early to optimize something.

Upvotes: 2

Related Questions