3 ms·
Can you tell us more about your production environment? Like how much data, average IOPS, and uptime requirements? I've been poking around and I can't find any
by jdcarter 10y ago
Can you tell us more about your production environment? Like how much data, average IOPS, and uptime requirements? I've been poking around and I can't find any real info on who's using this or how. The project's interesting and I'd love to hear more.
- jusob 10y agoI use it to store many small files (JSON and images). My requirements were: 1. predictable read time 2. read/write access through LAN 3. server easily installable on VPS 4. simple API The main downsides I found so far: 1. Master splitting are very hard to recover from. They happen rarely but when it does, be ready to restart master many times in random order. Latest version seems to have fixed it 2. No easy way to list the content of a volume. You need to use the command line on the volume files 3. Cleanup is hard (compacting the volume files), I fee that the GarbageThreshold is not working well 4. Hard to resize the volumes (i.e. set lower limits) after it has been started 5. Replication, as I mentionned in another comment Overall it works fine for me. The potential alternative (not fully tested) was Cassandar (the 64MB limit per object when I checked is fine with me).