Are you running multiple `arangoimp` jobs hitting the same collection concurrently? The trouble with this is that currently we have collection level locks, which serialise such requests. Maybe the chunk sizes we are using with `arangoimp` are too large, such that one `arangoimp` job has to wait for more than 15s on the write lock held by another one and therefore timeout. Could this be the case?
-- You received this message because you are subscribed to the Google Groups "ArangoDB" 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.
