General compilation of Mesos takes ~2GB per simultaneous job (-j N) being
used. In general if you have a host with less than 4GB of ram on it, you
probably won't be able to compile Mesos even doing it completely
sequentially.
That said, that instance has 15GB of ram, so it shouldn't be an issue
directories also?
On Tue, Dec 2, 2014 at 3:02 PM, Cody Maloney c...@mesosphere.io wrote:
Mesos inside docker definitely can work. There are some issues with the
slave in some cases (You can't have any containers which start with
'mesos-' on the slave, don't put two slaves on the same host.
https
Already filed one for this: https://issues.apache.org/jira/browse/MESOS-2166
On Mon, Dec 15, 2014 at 9:52 PM, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
Sorry for the delay! Probably you just don't have the 'perf' command
available on your machine, and the error is being poorly reported.
Actually back to GCC 4.4 is going to be supported for Mesos 0.21. Post 0.21
the plan is currently GCC 4.6 at a minimum, 4.7 if we can get that working
well (There are some issues in how Future is currently implemented), so
that a Debian Wheezy stable compiler will work.
On Sat, Dec 27, 2014 at
paths
using more of C++11 are enabled when gcc 4.8+ is used.
On Sat, Dec 27, 2014 at 10:11 AM, Cody Maloney c...@mesosphere.io wrote:
Actually back to GCC 4.4 is going to be supported for Mesos 0.21. Post
0.21 the plan is currently GCC 4.6 at a minimum, 4.7 if we can get that
working well
/local and have our own build of mesos.
Thanks again for your help. Are there specific Jira issues I can monitor?
I'm building a messaging infrastructure and mesos is the foundation.
-ag
Sent from my iPhone
On Feb 4, 2015, at 8:32 PM, Cody Maloney c...@mesosphere.io wrote:
Some
Also see https://issues.apache.org/jira/browse/MESOS-2129 if you want to
track progress on changing this.
Unfortunately it is on hold for me at the moment to fix.
Cody
On Wed, Jan 21, 2015 at 2:07 PM, Ryan Thomas r.n.tho...@gmail.com wrote:
Hey Dan,
The UI will attempt to pull that info
Running mesos slave inside of a docker container and having working slave
task recovery isn't supported at the moment. See:
https://issues.apache.org/jira/browse/MESOS-2115
On Mon, May 18, 2015 at 4:47 AM, Grzegorz Graczyk gregor...@gmail.com
wrote:
3-node cluster
CoreOS 675.0.0
Mesos 0.22.1
know Mesosphere will be at
least doing this, we may be able to provide it to others).
On Fri, Apr 10, 2015 at 12:12 PM, Cody Maloney c...@mesosphere.io wrote:
For Debian Wheezy support the plan is to just use Clang 3.5+ since we can
get a modern version of that onto the hosts fairly easily
As discussed in the last community meeting, we'd like to bump the minimum
required compiler version from GCC 4.4 to GCC 4.8.
The overall goals are to make Mesos development safer, faster, and reduce
the maintenance burden. Currently a lot of stout has different codepaths
for Pre-C++11 and
the canonical domain? https://downloads.mesosphere.com
appears to present a certificate for *.mesosphere.io.
On Wed, Jun 17, 2015 at 2:05 PM, Cody Maloney c...@mesosphere.io wrote:
Thanks for posting this. mesosphere.io should be back up now, and
mesosphere.io/downloads now working.
I would
https://downloads.mesosphere.com should start working as the DNS finishes
propogating. Should be used for the future (Going to get our website links
and the like updated).
Cody
On Thu, Jun 18, 2015 at 3:39 PM Cody Maloney c...@mesosphere.io wrote:
yes, downloads.mesosphere.io is the correct
Thanks for posting this. mesosphere.io should be back up now, and
mesosphere.io/downloads now working.
I would note that the mesosphere website, downloads now live at the domain '
mesosphere.com'. Normally mesosphere.io redirects, but that bit of
infrastructure unfortunately broke.
Cody
On Wed,
The Mesosphere packages use mesos-deb-packaging to build them, currently at
commit 4897858c4d93d3c6be1cad23bdea40c13d60e3bc.
The only additional piece that is added is some wrapper scripts to spin up
AWS machines, install the necessary dependencies, then run the build in
those VMs, then do a
The s3 fetcher stuff inside of DC/OS is not supported. The `hadoop` binary
has been entirely removed from DC/OS 1.8 already. There have been various
proposals to make it so the mesos fetcher is much more pluggable /
extensible (https://issues.apache.org/jira/browse/MESOS-2731 for instance).
For DC/OS we do two pieces. We simplify Mesos' log output via a module so
that it doesn't have any of it's internal logrotate logic, and just writes
to a single straight output file. We also include a mesos module so that
mesos task output goes to systemd journald, making it so every piece of
16 matches
Mail list logo
