[
https://issues.apache.org/jira/browse/CASSANDRA-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833080#action_12833080
]
Scott White commented on CASSANDRA-788:
---------------------------------------
Understood. But couldn't one make the counter argument that by forcing
snapshots to the same volume as the live data you could end up in one of two
scenarios:
1) Your snapshotted data has eaten up so much of the existing volume that
cassandra fails as it tries to add more data because there is no more disk left.
2) The live data has filled up so much of the existing volume that there is not
enough room left to do a snapshot?
It seems to me you can shoot yourself in the foot either way but having more
flexibility in which risk you are most susceptible becomes an explicit choice.
> Make snapshot dir location configurable
> ---------------------------------------
>
> Key: CASSANDRA-788
> URL: https://issues.apache.org/jira/browse/CASSANDRA-788
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Scott White
> Priority: Minor
>
> The snapshot dir location is currently hardwired to data/snapshots. It would
> be more convenient if this could be specified in a config file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
