joerg84

18 ms·

1. 1.▲
   by joerg84 7y ago

   Did you try the Kubernetes Operator: https://github.com/arangodb/kube-arangodb ? Should at least help with the k8s part... Also would be curious about your sharding challenges, feel free to ping me on the ArangoDB slack
2. 2.▲
   by joerg84 7y ago

   One of the authors here: Feel free to checkout the meetup talk https://www.meetup.com/Knowledge-Graphs-Meetup/events/264962... and the corresponding slides: https://docs.google.com/presentation&#x2
3. 3.▲
   by joerg84 8y ago

   cgroup limits can still be beneficial, consider for example contraining the (by default unlimited) metaspace.
4. 4.▲
   by joerg84 8y ago

   IMO these are a great improvement but one still needs to be aware of the underlying container limits. E.g., understanding why setting MaxRAMFraction=1 might not be a good idea as the container might get killed...
5. 5.▲
   by joerg84 9y ago

   One of the authors here: First of all thanks for the great disucssion here, it really motivated to write another follow-up article. There were some comments asking for more practical advice which is totally fair as this was supposed to be
6. 6.▲
   by joerg84 9y ago

   One of the authors here: This is the OpenJDK 8 implementation: http://hg.openjdk.java.net/jdk8/jdk8/hotspot/file/tip/src/os...
7. 7.▲
   by joerg84 10y ago

   "- Bundling-in the orchestration with docker make k8s or Mesos more inclined to fork docker and pull out unnecessary cruft." Mesos 1.0 already introduced the universal containerizer, allowing to run many docker images natively wit