haeaeae/duplicati
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Final eviction should always happen, and some caching is always needed in the new restore flow

Browse Source
This commit is contained in:
Carl Johnsen
2025-08-10 07:39:22 +02:00
parent 4c9f78f839
commit 537ee9c4cb
1 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Duplicati/Library/Main/Operation/Restore/VolumeManager.cs
+4 -6
View File
@@ -191,11 +191,8 @@ namespace Duplicati.Library.Main.Operation.Restore
{
case BlockRequestType.CacheEvict:
{
if (cache_max > 0)
{
Logging.Log.WriteExplicitMessage(LOGTAG, "VolumeRequest", "Evicting volume {0} from cache by request", request.VolumeID);
handle_evict(request.VolumeID);
}
Logging.Log.WriteExplicitMessage(LOGTAG, "VolumeRequest", "Evicting volume {0} from cache by request", request.VolumeID);
handle_evict(request.VolumeID);
}
break;
case BlockRequestType.DecompressAck:
@@ -222,7 +219,8 @@ namespace Duplicati.Library.Main.Operation.Restore
else
{
// Check if downloading another volume would exceed cache limits.
if ((cache.Count + in_flight_downloads.Count) >= cache_max)
// Cache_max = 0 auto evicts when all of the requests have been ack'ed.
if (cache_max > 0 && (cache.Count + in_flight_downloads.Count) >= cache_max)
{
Logging.Log.WriteVerboseMessage(LOGTAG, "VolumeRequest", null, "Evicting volume");
// TODO switch based of the eviction strategy.