I've a Mesos cluster which is having 3 master nodes & 20 agent nodes. Now i wanted to deploy "marathon" frameworks in it. I mean in multiframework Mesos cluster is there any limitations for specific number? In-terms of Mesos or Marathon?
Is there any restriction that for one agent node , we can deploy only one Marathon framework?
There is no limitation for number of frameworks.
Related
I have a mesos cluster with 1 master and 1 slave.
I followed this tutorial to set up the configuration of both the master and the slave. And I can see the Mesos Web UI in http://master:5050 and the marathon UI in http://master:8080.
Also Activated=1, which means that the mesos slave is successfully connected to the mesos master I guess.
However In the Resources section, the Offered property is always equal to 0.
The total amount of available CPU is 4. 13GB of RAM and 38GB of disk.
Can anyone help with this issue ?
We are running a 3 node mesos cluster and mesos master is running on each node. Also, 2 slaves are running on each node. Is this a good practice? 2 slaves on each cluster won't be sending too much offer and end up being overloaded? What is the recommended config for 3 nodes cluster?
Thread from Mesos User Mailing List
It depends on your isolation setting (mainly cgroup, or any node level
resources). In general, we don't recommend folks use multiple agents on a
node.
It's possible to make it work by setting cgroup_root separately for
MesosContainerizer. For DockerContainerizer, currently, we hard code
DOCKER_NAME_PREFIX, making it not possible to use two agents on a node
properly.
Running Docker containers won't work properly because restarting one agent
will cause Docker containers managed by the other agent to be deleted.
The instructions for installing Mesosphere DC/OS on AWS use a CloudFormation template where the minimum configuration indicates:
You have the option of 1 or 3 Mesos master nodes.
5 private Mesos agent nodes is the default.
1 public Mesos agent node is the default.
For our POC, as not to incur too much up-front cost, is it possible to do this all with two nodes? One for DC/OS and the other containterized with ElasticSearch and Kafka?
If not, what would be a good configuration for this type of architecture?
DC/OS does not run on Docker Swarm or Kubernetes. But you can run a development docker-in-docker local deployment on linux (or in a VM on mac/windows): dcos-docker
You could then install ElasticSearch and Kafka on top of DC/OS.
You could also use dcos-vagrant to run a multiple VM DC/OS local dev cluster.
Warning: the current vagrant v1.9.1 has a crippling centos network bug, if you need a VM. dcos-vagrant has a monkey patch workaround included, dcos-docker does not.
I have a cluster setup with nodes that are not reliable and can go down (They are aws spot instances). I am trying to make sure that my application master only launches on the reliable nodes (aws on demand instances) of the cluster. Is there a workaround for the same? My cluster is being managed by hortonworks ambari.
This can be achieved by using node labels. I was able to use the property in spark spark.yarn.am.nodeLabelExpression to restrict my application master to a set of nodes while running spark on yarn. Add the node labels to whichever nodes you want to use for application masters.
Marathon and Mesos do not support muti-datacenter. We are trying to find a way go around it. Can we run mesos in each data centersand have marathon talk to all the mesos from difference data centers?
So far marathon only could use one Mesos Master. Maybe you could combine your Mesos clusters to a big Mesos cluster.