Its not so much a matter of want to isolate them, I may not be able to due to
limitations outside of my control which may require them to be on their own
private network.
From: Marco Massenzio [mailto:ma...@mesosphere.io]
Sent: Tuesday, July 21, 2015 12:47 PM
To: user@mesos.apache.org
Subject:
Not too worried. I could of course have only the two other machines running as
both Master and Slave for instance, but if I could incorporate the desktop into
the cluster as well I think that would be preferable so that the other two can
run as complete slaves and I can offload all of my
You're not crazy :)
This will work just fine, the Master takes up very little CPU/RAM, and, as
you plan to have it on your desktop you could even wrap with some
send-notify script so that should it fail or something, you could get an
alert.
I'm not sure why you want to segment out the Agent Nodes
There's nothing stopping you running the mesos master and slave process on the
same machine, so you could run the master process on your non-desktop machine
if you're worried.
We have the master and slave processes run as docker containers and they can
both end up on the same machine without
+1 (binding) to Mesos 0.23.0-rc4 as 0.23.0
As I mentioned before, for rc3, basic integration tests passed for Mesos 0
.23.0 on CoreOS with DCOS GUI/CLI, Marathon, Chronos, Spark, HDFS,
Cassandra, and Kafka.
We have been tracking the Ubuntu `sudo make check` failures in
See below regarding the mesos slaves
_
From: Dvorkin-Contractor, Eugene (CORP) eugene.dvorkin-contrac...@adp.com
Sent: Friday, July 17, 2015 11:21 AM
Subject: How to update mesos slave configuration
To: user@mesos.apache.org
Hi,I have a
Eugene,
If the new storage is on another drive, you will only be able to use one of
the devices for Mesos sandboxes. You can change the --work_dir to point to
the new storage and everything for Mesos will be stored there. This
includes the checkpointed slave state and every task's sandbox. You
Nastoo, the only other option right now is to recompile Mesos with those
hardcoded constants changed to your desired value. Painful, but that's why
we wanted to turn them into flags.
https://github.com/apache/mesos/blob/0.22.1/src/master/constants.cpp#L34
On Fri, Jul 17, 2015 at 4:15 PM, Nastooh
Is there likely to be any issues with the Master? Given it would be an active
desktop it would be running all of the typical mesos master stuff, plus say an
active Ubuntu desktop environment. It would also need to host things like a
local Docker registry and the like as well, since the compute
As far as mesos is concerned, compute is a commodity. This should work just
fine. Put Aurora or Marathon ontop of mesos if you need a general purpose
scheduler and you're good to go. The nice thing is that you can add
additional slaves as you need. I believe heterogeneous clusters are best if
Let's say I had 2 high-performance workstations kicking around (dual 6-core,
2.4GHz, xeon processors; 128 GB RAM each; etc) and a smaller workstation
(single Xeon 4-core, 3.5GHz and 16 GB RAM) available and I wanted to cluster
them together with Mesos. What is the best way of doing this? My
11 matches
Mail list logo
