4 ms·

This is rather cool, but data in ArangoDB will not survive docker container restart, so, sadly, this setup is still just a toy.

mateuszf 12y ago
It's possible to use volumes functionality to keep db data persistent.
- m_mueller 12y ago
  That's a rather large overlook in a tutorial for a DBMS based app though.
- sargun 12y ago
  But, it wont be persisted across restarts in Mesos-land, because Mesos doesn't have the idea of data volumes. The way that Google (Omega) gets around this is having GFS deal with replication, and persisting all of their databases into the shared file system.
  - don71 12y ago
    There is an interesting discussion on the mailing list http://mail-archives.apache.org/mod_mbox/mesos-user/201410.mbox/%3CCAC2U_Pfc-11zV0OK=-4Ha6mau3XLwX-LhiggJLTM4ATxAGE9XQ@mail.gmail.com%3E http://mail-archives.apache.org/mod_mbox/mesos-user/201410.m...
- googamooga 12y ago
  In order to use docker volume you have to stick your ArangoDB docker instance to exact same mesos worker. Otherwise database instance may be started by marathon on any random chosen worker, without saved volume. IMHO, sticking database instance to exact cluster node renders whole idea of using mesos and marathon completely useless.
  - lhc- 12y ago
    You could mount a network volume on all your mesos hosts and make that available to the DB container, so that no matter which host handles that job, your data will persist easily.
    - tinco 12y ago
      What would the performance characteristics of that be? What configures the network volume? Isn't configuring and maintaining a network volume comparable to configuring and maintaining a database? Mesos is missing something to deal with persistent storage. From what I've heard all teams that employ Mesos don't actually run their persistant storage clusters in Mesos. Perhaps handy for them, but for me that takes most of the use out of Mesos.
      - aabhay 12y ago
        Mesosphere's DNS implementation (https://github.com/mesosphere/mesos-dns https://github.com/mesosphere/mesos-dns) helps address that problem. You can use dns routing to create an internal storage or implement a cache that routes cache misses to an external store.
        googamooga 12y ago
        Mesos-DNS has nothing to do with data persistance on mesos. It is just another implementation of cluster service locator.

mateuszf 12y ago

It's possible to use volumes functionality to keep db data persistent.

m_mueller 12y ago
That's a rather large overlook in a tutorial for a DBMS based app though.
sargun 12y ago
But, it wont be persisted across restarts in Mesos-land, because Mesos doesn't have the idea of data volumes. The way that Google (Omega) gets around this is having GFS deal with replication, and persisting all of their databases into the shared file system.
- don71 12y ago
  There is an interesting discussion on the mailing list http://mail-archives.apache.org/mod_mbox/mesos-user/201410.mbox/%3CCAC2U_Pfc-11zV0OK=-4Ha6mau3XLwX-LhiggJLTM4ATxAGE9XQ@mail.gmail.com%3E http://mail-archives.apache.org/mod_mbox/mesos-user/201410.m...
googamooga 12y ago
In order to use docker volume you have to stick your ArangoDB docker instance to exact same mesos worker. Otherwise database instance may be started by marathon on any random chosen worker, without saved volume. IMHO, sticking database instance to exact cluster node renders whole idea of using mesos and marathon completely useless.
- lhc- 12y ago
  You could mount a network volume on all your mesos hosts and make that available to the DB container, so that no matter which host handles that job, your data will persist easily.
  - tinco 12y ago
    What would the performance characteristics of that be? What configures the network volume? Isn't configuring and maintaining a network volume comparable to configuring and maintaining a database? Mesos is missing something to deal with persistent storage. From what I've heard all teams that employ Mesos don't actually run their persistant storage clusters in Mesos. Perhaps handy for them, but for me that takes most of the use out of Mesos.
    - aabhay 12y ago
      Mesosphere's DNS implementation (https://github.com/mesosphere/mesos-dns https://github.com/mesosphere/mesos-dns) helps address that problem. You can use dns routing to create an internal storage or implement a cache that routes cache misses to an external store.
      - googamooga 12y ago
        Mesos-DNS has nothing to do with data persistance on mesos. It is just another implementation of cluster service locator.