mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

avoid using cluster nodes in drop proof when dropping from cluster

Browse source 
This is obviously necessary in order for dropping from a cluster to be able to
drop from all nodes.

It also avoids violating numcopies when a cluster node is a special remote.
If it were used in the drop proof, nothing would prevent the cluster from
dropping from it.
This commit is contained in:
Joey Hess 2024-06-23 06:20:11 -04:00
parent 5a4b4b59b9
commit 7bbd822a17
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 24 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/todo/git-annex_proxies.mdwn
View file

@ -70,16 +70,6 @@ For June's work on [[design/passthrough_proxy]], implementation plan:
* Implement cluster drops, trying to remove from all nodes, and returning
which UUIDs it was dropped from.
Problem: May lock content on cluster
nodes to satisfy numcopies (rather than locking elsewhere) and so not be
able to drop from nodes. Avoid using cluster nodes when constructing drop
proof for cluster.
Problem: When nodes are special remotes, may
treat nodes as copies while dropping from cluster, and so violate
numcopies. (But not mincopies.) This is also solved by avoiding using
cluster nodes when constructing drop proof for cluster.
Problem: `move --from cluster` in "does this make it worse"
check may fail to realize that dropping from multiple nodes does in fact
make it worse.