[
https://issues.apache.org/jira/browse/CASSANDRA-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115834#comment-14115834
]
Brandon Williams commented on CASSANDRA-7239:
---------------------------------------------
Still seeing a decent amount of discrepancy:
{noformat}
root@bw-2:/srv/cassandra# du -sh
/var/lib/cassandra/data/Keyspace1/Standard1-967836f02fbe11e4ae61517bcdb23258/
9.7G
/var/lib/cassandra/data/Keyspace1/Standard1-967836f02fbe11e4ae61517bcdb23258/
root@bw-2:/srv/cassandra# bin/nodetool status
Note: Ownership information does not include topology; for complete
information, specify a keyspace
Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns Host ID
Rack
UN 10.208.35.225 6.59 GB 256 100.0%
43ab5b6b-7248-4960-911f-bd8620ca83a6 rack1
{noformat}
But no negative load.
> Nodetool Status Reports Negative Load With VNodes Disabled
> ----------------------------------------------------------
>
> Key: CASSANDRA-7239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7239
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: 1000 Nodes EC2 m1.large ubuntu 12.04
> Reporter: Russell Alexander Spitzer
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: 0001-add-new-sstable-size-when-rewriting.patch,
> nodetool.png, opscenter.png
>
>
> When I run stress on a large cluster without vnodes (num_token =1 initial
> token set) The loads reported by nodetool status are negative, or become
> negative after stress is run.
> {code}
> UN 10.97.155.31 -447426217 bytes 1 0.2%
> 8d40568c-044c-4753-be26-4ab62710beba rack1
>
> UN 10.9.132.53 -447342449 bytes 1 0.2%
> 58e7f255-803d-493b-a19e-58137466fb78 rack1
>
> UN 10.37.151.202 -447298672 bytes 1 0.2%
> ba29b1f1-186f-45d0-9e59-6a528db8df5d rack1
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
