Sync and Concurrent Read and Write AWS S3

[moleacit]

On MountainDuck and our Files are on S3 Mounted to Windows.

users concurrently updating the same files not getting locked even locked option is selected in the settings.
users not getting the latest updated files thus overwriting old files making new, conflict does not appear.
users updated files but not synced to s3

despite we keep the cache 1 day and minimum 500MB and putting things online the cache size keep growing and users ran out of disk space.

[dkocher]

For S3 only Pseudo Locking ¹ is supported for selected file types only. Conflict detection is expected to work as S3 provides checksums for files. You should see previous versions of files moved away with a timestamp in the filename on conflict. Additionally we suggest to enable S3 versioning on the bucket. For additional help please reach out to our support team.

Footnotes

1. https://docs.mountainduck.io/mountainduck/locking/#pseudo-locking-for-protocols-with-no-native-lock-support-using-lock-owner-files ↩