You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ian Soboroff (JIRA)" <ji...@apache.org> on 2010/06/04 19:28:58 UTC

[jira] Issue Comment Edited: (CASSANDRA-1161) Data file quotas

    [ https://issues.apache.org/jira/browse/CASSANDRA-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875670#action_12875670 ] 

Ian Soboroff edited comment on CASSANDRA-1161 at 6/4/10 1:28 PM:
-----------------------------------------------------------------

I agree this isn't the best solution, btw, because to actually work the limit has to be to have enough free space to anticompact the largest db file.

So let me rephrase my tradeoff question - what's the tradeoff between fewer larger db files, and more smaller ones?  The latter would be quicker to anticompact (and compact), and easier to recover from in case of corruption.  Linear scans of all dbs on a node become somewhat more expensive since each db costs an open().  Beyond this, I don't know the internal architecture of the storage layer to hypothesize.

If one can place a quota on the size of a single db file, then it's easy to make sure enough space is reserved for an anticompaction.


      was (Author: isoboroff):
    I agree this isn't the best solution, btw, because to actually work the limit has to be to have enough free space to anticompact the largest db file.

So let me rephrase my tradeoff question - what's the tradeoff between fewer larger db files, and more smaller ones?  The latter would be quicker to anticompact (and compact), and easier to recover from in case of corruption.  Linear scans of all dbs on a node become somewhat more expensive since each db costs an open().  Beyond this, I don't know the internal architecture of the storage layer to hypothesize.
  
> Data file quotas
> ----------------
>
>                 Key: CASSANDRA-1161
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1161
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.6.2
>            Reporter: Ian Soboroff
>
> Since anticompaction may require significant disk space, it would be nice to be able to specify a disk quota.
> A simple quota option supporting literal and percentage quantities would be nice, but I think a better approach would be an option to not allow a Data.db file to grow larger in size than the existing free space on the volume.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.