You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Dmitry Tsechoev (JIRA)" <ji...@apache.org> on 2014/06/11 08:43:01 UTC

[jira] [Updated] (CASSANDRA-7376) Lack of disk space during the the utility 'nodetool rebuild'

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

Dmitry Tsechoev updated CASSANDRA-7376:
---------------------------------------

    Summary: Lack of disk space during the the utility 'nodetool rebuild'  (was: Lack of disk space during the the utility nodetool rebuild)

> Lack of disk space during the the utility 'nodetool rebuild'
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-7376
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7376
>             Project: Cassandra
>          Issue Type: Task
>          Components: Tools
>            Reporter: Dmitry Tsechoev
>
> Good afternoon.
> I apologize in advance if my question is irrelevant.
> In a production environment we use Cassandra 2.0.7.
> Initially we were enough one node (cass-05, the local IP-address 192.168.0.5). There is now a need for a second node (cass-06, the local IP-address 192.168.0.6).
> For the second node (cass-06) have a separate server.
> Cassandra settings on cass-06 are completely analogous to the cass-05.
> Used NetworkTopologyStrategy replication strategy. Each node is configured on it's own rack and data center with 1 copy of the data (rack1, DC1: 1 for cass-05 and rack2, DC2: 1 for cass-06).
> 1TB of disk space is available for Cassandra on each server.
> On the server cass-05 have 600Gb of real data.
> On the server cass-06 we run utility 'nodetool rebuild':
> {{#./nodetool -h192.168.0.6 rebuild -- DC1}}
> Cassandra on cass-06 begins to create a large number of temporary files for the tables that it, in theory, should be removed. However, for some reason it does not.
> 9-12 hours through the entire 1TB disk space occupied by these temporary tables, which leads to malfunction node.
> After restarting the Cassandra on the cass-06 node the disk space is occupied only 150Gb.
> During the utility 'nodetool rebuild' node cass-06 is involved in write/read as well as cass-05.
> Thanks for any help.



--
This message was sent by Atlassian JIRA
(v6.2#6252)