JoaoJandre commented on issue #8907: URL: https://github.com/apache/cloudstack/issues/8907#issuecomment-2074978778
> > > Ok, one more, will coalescing of snapshots on secondary be implemented at all? (and do we think we need it?) > > > > > > I don't see a reason to coalesce snapshots on secondary. We would be losing the option to revert to a snapshot in the middle of the chain. > > The only exception is when creating a template/volume from snapshot, in this case, to not mess too much with the current implementation, we will create a temporary coalesced snapshot before sending the command to the SSVM. But after the template/volume is created, the temporary coalesced snapshot will be removed. > > one thing I was thinking of is when chains become very long , e.g. an automatic snapshot with scheduled deletes. Just a thought though, we can burn that bridge ones we try to cross it. The chain size will be controlled by `snapshot.delta.max` (which has a pretty high default value in my opinion). When the chain reaches this threshold, a new one will be created, that is, a new full snapshot will be taken and the next snapshots will be based on this one. About the snapshot policies, this is covered a little by section 2.1.1. But when the `maxSnaps` is reached, the old snapshots will start to get removed (still following the deletion rules on section 2.4). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
