[
https://issues.apache.org/jira/browse/CASSANDRA-7984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143053#comment-14143053
]
Ashic Mahtab commented on CASSANDRA-7984:
-----------------------------------------
Yup...definitely on 2.1.0. Reproduced on two separate clusters. The nodetool
status and the opscenter screenshots attached are from two different clusters
both running 2.1.0. Running Opscenter 5.0.1 as well.
It's it's something ridiculous like -99343439 bytes, then it's obvious. Trouble
is, I just found that one node was 9MB while others were ~45MB. Restarting the
9MB node and it jumped back up to ~45 MB.
> Nodetool status sometimes reports negative size
> -----------------------------------------------
>
> Key: CASSANDRA-7984
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7984
> Project: Cassandra
> Issue Type: Bug
> Components: Core, Tools
> Environment: Ubuntu server x64, 4 nodes on 4 VMWare VMS, 2GB ram on
> each node.
> Reporter: Ashic Mahtab
> Attachments: Capture.PNG, Capture2.PNG
>
>
> This has been an issue for a few versions now (from the various RCs of 2.1,
> but possibly earlier). The issue doesn't manifest itself initially, but if
> the cluster is left alone for a while, slowly but surely it pops up. The
> issue is that nodetool status starts outputting negative values for Load.
> This causes the graphs in OpsCenter to start acting crazy as well. I've
> attached screenshots of both.
> Running a rolling restart (or simply restarting the affected node) resolves
> the issue until it arises again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
