cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lyuben Todorov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-6418) auto_snapshots are not removable via 'nodetool clearsnapshot'
Date Thu, 05 Dec 2013 12:07:36 GMT

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

Lyuben Todorov updated CASSANDRA-6418:
--------------------------------------

    Attachment: 6418_v2.patch

Not sure why my ant missed that build problem. Added Keyspace#clearCfSnapshot that takes an
extra cfName argument, and also the above nits are tackled in v2. 

> auto_snapshots are not removable via 'nodetool clearsnapshot'
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-6418
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6418
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>         Environment: auto_snapshot: true
>            Reporter: J. Ryan Earl
>            Assignee: Lyuben Todorov
>            Priority: Minor
>             Fix For: 2.0.4
>
>         Attachments: 6418_cassandra-2.0.patch
>
>
> Snapshots of deleted CFs created via the "auto_snapshot" configuration parameter appear
to not be tracked.  The result is that 'nodetool clearsnapshot <keyspace with deleted CFs>'
does nothing, and short of manually removing the files from the filesystem, deleted CFs remain
indefinitely taking up space.
> I'm not sure if this is intended, but it seems pretty counter-intuitive.  I haven't found
any documentation that indicates "auto_snapshots" would be ignored by 'nodetool clearsnapshot'.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message