[
https://issues.apache.org/jira/browse/CASSANDRA-14996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754459#comment-16754459
]
Blake Eggleston commented on CASSANDRA-14996:
---------------------------------------------
This doesn’t seem like the right solution to the problem you’re describing. If
I understand incremental backup correctly, occasionally skipping hard link
creation defeats the purpose and will leave you with an incomplete backup and
lost data on recovery.
The real problem seems to be that you don’t notice that your backup system has
failed or your nodes are out of disk space until nodes start falling over. I'd
probably start by putting some monitoring and alerts around your cluster and
backup system.
> Incremental backups can fill up the disk if they are not being uploaded
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-14996
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14996
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Shaurya Gupta
> Priority: Major
> Attachments: patch_CASSANDRA-14996, patch_CASSANDRA-14996.html
>
>
> This creates a major problem if the script which uploads the snapshots is
> triggered via some API and the application triggering it is somehow down and
> is not able to hit the API. This affects Cassandra and slowly one or more
> Cassandra nodes go down.
> There could be a check in Cassandra that before creating a snapshot it checks
> that the disk has some sufficient (configurable via cassandra.yaml and jmx)
> disk space.
> This could be achieved by making change in
> public void maybeIncrementallyBackup(final Iterable<SSTableReader> sstables)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
