• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

What to use instead of Mesos for Databases or Jenkins?

 
Ranch Hand
Posts: 162
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, Roger. I noted in the sample chapter 1 that Mesos isn't a good candidate for managing database clusters. Other than the products provided by the various DB vendors (some of which are really hard to use and
cause a lot of heartburn when deploying new releases), what would you recommend as a "Mesos quality manager" for things that Mesos doesn't do well?
 
Greenhorn
Posts: 11
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
To be honest, I suppose that all depends on the technology. Systems like Ceph, HDFS, Cassandra, and Elasticsearch, where fault tolerance is built into the service, should work just fine running on Mesos (and Marathon). Just be sure to run each instance of the overall cluster on a dedicated machine, so that you don't inadvertently create single points of failure. And of course, take backups (and test them!)

For services that require some sort of underlying storage, you have a couple of options: if you're in an enterprise environment where you can get a NFS export off of a SAN (or some other storage cluster), your best bet might be to ensure that this mount exists on each machine in the cluster and use that as a sort of shared storage, mounting a directory from the NFS export into the container. As a matter of fact, this is what we (Mesosphere) currently suggest for our customers running Jenkins on DC/OS.

If that's not an option, or you're running in AWS, you might take a look at their latest offering EFS, which essentially does the same thing. The team over at EMC has also produced the open source tool REX-Ray (http://rexray.readthedocs.io/en/stable/) which is *fantastic* for provisioning a storage volume and attaching it to a running instance. If the instance is restarted, it simply reattaches to the volume before it comes up in a fully automated way; less work on your part!
reply
    Bookmark Topic Watch Topic
  • New Topic