Off the top of my head I don't see any reason why two camputs could not concurrently upload to Camlistore, so the fact that they mutually exclude each other because of their stat/have caches should probably be considered a bug, and be fixed.
In the meantime, I think you should be able to make things work without having to disable the caches by: 1) either run each camput with their own cache dir, by setting the CAMLI_CACHE_DIR (default on linux is $HOME/.cache/camlistore) env var differently for each. or 2) run each camput in isolation, e.g. each in a docker container On 28 July 2017 at 22:24, Altaf Kassam <[email protected]> wrote: > > On Friday, July 28, 2017 at 9:51:45 AM UTC-7, mpl wrote: >> >> >> if you set CAMLI_DEBUG, you can also set -statcache=false (see >> https://camlistore.org/cmd/camput/files.go#L94) >> >> > > Thanks for the suggestion on disabling stat cache. This seems to have > addressed the concurrency issue, however, we will evaluate the impact that > disabling of the caches has on our system. As a follow-up to anyone else who > is having the same issue, the following call to camput will bypass both > havecache and statcache, allowing for concurrency at the process level: > > export CAMLI_DEBUG=true > camput -havecache=false file -statcache=false > > Outside of running in debug mode, are there any best practices that allow > for concurrency at the process level in Camlistore? > > -- > You received this message because you are subscribed to the Google Groups > "Camlistore" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
