Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.3.1.
The CHANGELOG for the release is available at:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.3.1-rc1
This is generally not something we want users to do (i.e. leak something
outside of their container).
Mesos will kill all tasks in the cgroup if you're using cgroup isolation,
so you would have to ensure the daemon escapes the cgroup. If you're using
the posix isolation, you also need to be sure
Hadoop definitely seems to be on the list of frameworks for mesos:
http://mesos.apache.org/documentation/latest/frameworks/
Has anyone recently tested getting it to work?
On Thu, Jul 27, 2017 at 5:39 PM, Stephen Gran
wrote:
> Hi,
>
> On 27/07/17 13:54, Traiano
Typically a framework with no role cannot use resources reserved for
another role. So, it would be interesting to see what happened.
Also, please be aware that directly upgrading from 0.28.0 to 1.3.0 is not
supported. You need to go from 0.28.0 to 1.0.0 and then jump from 1.0.0 to
1.3.0.
On Fri,
Hi All
The latest version of mesos fails to build on Ubuntu 14.04.5. make fails
with the following error:
-
.
.
.
cp: cannot stat '../../src/python/cli/src/mesos/__init__.py': No such file
or directory
make[2]: *** [python/cli/src/mesos/__init__.py] Error 1
make[2]: Leaving directory
Hi,
we did a migration from Mesos 0.28 to 1.3.0 and somehow it looks like
one framework "stole" resources another framework had reserved earlier.
Unfortunately I do not have any logs for the time frame so I'm not
certain what exactly happened. Currently we have one framework running
with a
Hello,
I am trying to understand some basic components of Mesos and i have made some
notes corresponding to my conclusion. If somebody could check this out and
review them, or can provide me some more information about the specific topic i
would be thankful. Below you will find my notes.
-
7 matches
Mail list logo