Open Taepper opened 4 weeks ago
There are good utilities for this that are part of UNiX so we don't need to reinvent, using flock for example, which makes it easy for multiple SILO instances running on the same data folder to each lock and prevent deletion.
See details from quick Chatgpt exploratory session: https://chatgpt.com/share/670e0ab2-5c78-8005-9373-246d6002ad47
It's worth considering as part of implementing this whether having multiple SILO/LAPIS instances sharing a directory (with a load balancer, as Cornelius mentioned) is something you intend to support.
Currently there is no way for a user to know whether SILO (running as api) only requires the folder with the latest valid timestamp or also previous folder are required (due to being in transition from old to new / newer folders are corrupted due to a bug).
A locking mechanism in the form of a file could solve this problem