I'm not aware of any ports of MongoDB on Mesos, but the one gotcha to keep in mind when porting database frameworks is that the task/executor sandbox in Mesos is ephemeral. IOW, when an executor exits the sandbox gets cleaned up (not immediately but after certain time based on the garbage collection algorithm). So if a MongoDB executor writes its state/db in the sandbox then that data is irrecoverable if the task/executor terminates (e.g., LOST). Having said that, follow https://issues.apache.org/jira/browse/MESOS-1554 for future work in this area.
On Tue, Sep 2, 2014 at 2:50 PM, Ankur Chauhan <[email protected]> wrote: > Hi all, > > I apologise for the repost but wanted to get some responses. I am evaluating > mesos and wanted to know if anyone has successfully used > mesos (with or without docker) as a means of managing a mongodb deployment. > Currently, I have 8 shards where each shard is a 3x replicated replicaset and > contains > 500GB of data. > > > I was wondering if someone has tried to deploy and maintain a mongodb > deployment using mesos (or maybe tell me why this is not advisable), any > gotchas and preferred methodology for deployment. > > -- Ankur > >
