You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2012/09/26 15:23:07 UTC

[jira] [Resolved] (CASSANDRA-4722) Wrong file's size in nodetool netstats command

     [ https://issues.apache.org/jira/browse/CASSANDRA-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yuki Morishita resolved CASSANDRA-4722.
---------------------------------------

    Resolution: Won't Fix

Even if it's compressed, progress shows it as decompressed size of the transferring section.
Progress size is not always equal to file size, since most of the time nodes transfer part of the sstable.
>From v1.2, though, when transferring compressed file, cassandra sends it compressed. So progress size > actual file size won't happen. (see CASSANDRA-4297)
                
> Wrong file's size in nodetool netstats command
> ----------------------------------------------
>
>                 Key: CASSANDRA-4722
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4722
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>         Environment: Cassandra 1.1.4, Snappy compression, Leveled Compaction Strategy
>            Reporter: Alexey Zotov
>            Priority: Minor
>              Labels: leveled, nodetool
>
> Size of file calculated by 'nodetool netstats':
> {code}
> keyspace: /data/cassandra/data/keyspace/columnfamily/keyspace-columnfamily-he-12345-Data.db sections=1 progress=0/35356804 - 0%
> {code}
> Real size of file:
> {code}
> -rw-r--r--. 1 cassandra cassandra 20977068 Sep 24 06:04 /data/cassandra/data/keyspace/columnfamily/keyspace-columnfamily-he-12345-Data.db
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira