[Gluster-devel] autodelete in snapshots

Lalatendu Mohanty lmohanty at redhat.com
Tue Apr 15 13:48:36 UTC 2014

On 04/15/2014 07:05 PM, Raghavendra Bhat wrote:
> Hi,
> As of now, in snapshots there are 2 limits for the number of 
> snapshots, hard-limit and soft-limit. Usually soft-limit is 90% of 
> hard-limit by default (it can be changed also). Say the hard-limit is 
> 50, then soft-limit by default will be 45. We are planning to do 
> autodelete of the oldest snapshot upon reaching the limit.
> There are 2 options:
> 1) Start doing autodelete upon reaching the soft-limit. i.e If the 
> hard limit is 50 and the  number of the snapshots taken becomes 45, 
> then for the next snapshot taken (i.e 46th snapshot), the oldest 
> snapshot will be automatically deleted in the background.
> 2) Use soft-limit as a means to notify the admin about limit being 
> reached (gf_log, syslog etc, or also a warning message shown for every 
> snapshot taken after the soft limit is reached) and start doing 
> autodelete after reaching the hard-limit i.e once 50 snapshots are 
> reached, then when 51st snapshot is triggered, the oldest snapshot 
> will be deleted in the background.
> Please provide feedback.

I like the #2 option. If user has set something as hard-limit, it should 
be treated as hard limit and soft-limit can be used as warning mechanism.

> NOTE: The auto-delete can be made configurable, which if turned off, 
> snapshot create fails upon reaching the limit.
> Regards,
> Raghavendra Bhat
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> https://lists.nongnu.org/mailman/listinfo/gluster-devel

More information about the Gluster-devel mailing list