I am seeing # of read requests cluster wide in opscenter is much smaller than what nodetool cfstat's reported at Keyspace level at node level. How could this happen?
In an effort to consolidate free help offered for our products we have decided to move these forums to a more widely used forum. Please use one of the following queries (or any combination):
- Cassandra: tag search or plain text search
- DataStax Enterprise: tag search or plain text search
- DataStax OpsCenter: tag search or plain text search
are 61620/61621 ports configurable in community version of opscenter?(19 posts) (3 voices)
nodetool cfstats reports a total number of reads that node has done since it last started. OpsCenter is reporting the number reads per second that the whole cluster is doing. Does that explain the difference?
I calculated read requests per second by comparing nodetool cfstats(for whole keyspace) difference. So I don't understand why # of request per second at cluster level reported in opscenter is smaller than # of request per second at node level calculated from nodetool cfstat. # at cluster level should be bigger as it should be sum of # from all nodes.
The number that OpsCenter shows is also the number of writes/reads that are coordinated -- basically, it should be close to matching the number of writes/reads per second that your application is doing.
The number that cfstats reports are local read/write counts. This means that if you have RF=3, you'll see 3x as many reads/writes at the cfstats level.