Hi, if you do not change the default parameters then the ArangoDB tasks are deployed with very low resource limits (1GB memory and 1GB disk for each DBserver). Therefore, you can relatively quickly run into these limits and I suspect that this is what made one of your DBservers fail. Unfortunately, the crash seems to have corrupted a file in the write ahead log. Currently, there is no way how you can manually launch a task in the Mesos environment and the framework is not able to restart the tasks with `--database.ignore-datafile-errors true` as recommended in the logs. So there I can only recommend to redeploy the ArangoDB cluster with higher resource limits and try again. Sorry for the inconvenience. If you have further questions or the problems persist with higher limits, please ask again. Max.
-- 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.
