You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build out locator API that is ls with list of locations as part of metadata
also one for placing replicas, either:
expose known servers
modified PUT that instead of 409 will redirect to a server that doesn't have it yet
script takes a bucket and a min number of replicas
call API and if any below minimum, trigger a replication
use above replica placement (pull data and figure one out) or just PUT with appropriate switches
or user supplied targets
Option B:
no change to locator or object servers
replicator takes source servers, dest servers, and min number of replicas
source and dest may overlap or even be the same
go to each source and list and store files and metadata along with where each was found
error if hash doesn't match
go through list and check each dest server, if count is too low, pick from remaining servers appropriate place(s) to replicate (similar to current locator put logic)
Due to lack of locking #18#25 maybe refuse to replicate if no sha sum?
Activity
Basic bucket listing and replication
ctengel commentedon Oct 25, 2025
Pin
ctengel commentedon Jan 7, 2026
Next steps
From there the next part is build out a client/server system that:
Script to migrate from old to new checksum style
ctengel commentedon Jan 10, 2026
Option A:
Option B:
Due to lack of locking #18 #25 maybe refuse to replicate if no sha sum?
untested replication stuff
make new replicate code CLI