s5cmd sync -- any way for efficient --incremental ?

peak / s5cmd

Parallel S3 and local filesystem execution tool.

MIT License

2.64k stars 231 forks source link

s5cmd sync -- any way for efficient --incremental ? #746

Open yarikoptic opened 2 months ago

yarikoptic commented 2 months ago

We have a big (in TBs but also billions of keys) bucket to download/sync locally. FWIW, versioning turned on, so keys have versionIds assigned.

Is there some way to make sync efficient as to utilize some S3 API (or extra AWS service) to avoid listing/going through all keys it saw on the previous run, but rather operate on the "log" of the diff since prior state? (just get bunch of keys which were added or modified and some DeleteKey markers for deleted keys)

kabilar commented 10 hours ago

Hi @yarikoptic, it looks like this may have been previously addressed (issues: #441, #447; fix: https://github.com/peak/s5cmd/pull/483) and tested with the use cases of millions of files.

cc @puja-trivedi @aaronkanzer

yarikoptic commented 8 hours ago

code pointed there implies listing and sorting full bucket/destination first, not operating on "incremental"s
there they talk about thousands and a million of files, and concern of sorting those keys
I am talking about hundreds of millions or few billions of keys (that is where we are in DANDI ATM). Hence any solution requiring full listing first is doomed to be inefficient and expensive (if someone to pay for those listing queries).