://mesos.apache.org) will be updated shortly to reflect
this release.
Thanks,
-Adam-
On Wed, Nov 29, 2017 at 6:32 PM, Benjamin Mahler <bmah...@apache.org> wrote:
> +1 (binding)
>
> make check on macOS 10.13.1
>
> On Wed, Nov 29, 2017 at 9:17 PM, Adam Bordelon <a...@mesos
s://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/44/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Success]
> <https://build
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.2.3.
1.2.3 is our last scheduled bug fix release in the 1.2.x branch.
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.2.3-rc1
Please reply to this email if you have pending patches to backport to 1.2.x.
I'm aiming to cut a 1.2.3 next week. This will be the last 1.2.x release.
I see 3 JIRAs targeted for 1.2.3, but none of them look quite ready to land:
In the v0 API:
If the secret updates, you will need to reauthenticate with the new
credentials and reregister, perhaps triggered by knowing when the secret
will expire.
Changing the principal in FrameworkInfo will require you to register as a
new framework_id until
=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%
> 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Failed]
> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-
> Release/38/BUILDTOO
open.mesosphere.
> com/downloads/mesos-rc/#apache-mesos-1.2.2-rc1
>
> The following docker images based on Ubuntu 16.04 are also available:
> * mesosphere/mesos:1.2.2-rc1
> * mesosphere/mesos-master:1.2.2-rc1
> * mesosphere/mesos-agent:1.2.2-rc1
>
> Kapil
>
>
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 1.2.2.
1.2.2 includes the following:
* [MESOS-5187] - The filesystem/linux isolator does not set the
permissions of the
Hi all,
The vote for Mesos 1.2.1 (rc1) has passed with the following votes.
+1 (Binding)
--
Till Toenshoff
Benjamin Mahler
Adam Bordelon
+1 (Non-binding)
--
tommy xiao
There were no 0 or -1 votes.
Please find the release at:
https
FTFY: Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/1.3.0
On Wed, Jun 7, 2017 at 3:03 AM, Michael Park wrote:
> Hi all,
>
> The vote for Mesos 1.3.0 (rc3) has passed with the
> following votes.
>
> +1 (Binding)
> --
>
//builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/35/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=%28docker%7C%7CHadoop%29&&%28%21ubuntu-us1%29&&%28%21ubuntu-
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.2.1.
1.2.1 is a bug fix release. 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.2.1-rc1
The candidate for Mesos 1.2.1 release is available
-0, wish we could include the fix for
https://issues.apache.org/jira/browse/MESOS-7265 in 1.0.4, but I won't hold
the release for it.
On Mon, Apr 17, 2017 at 3:44 PM, Vinod Kone wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.0.4.
>
I found https://issues.apache.org/jira/browse/MESOS-7133 but that was
supposedly fixed in 1.1.1 (broken in 1.1.0)
On Tue, Mar 28, 2017 at 12:23 AM, Adam Cecile wrote:
> Hello,
>
>
> Here is a simple test showing why I cannot upgrade Mesos anymore (Debian
> Jessie, using
Hello devs and users,
The vote for Mesos 1.2.0 (rc2) has passed with the following votes:
+1 (Binding)
--
*** Adam B
*** Vinod Kone
*** Joseph Wu
-0
--
*** Jie Yu, for MESOS-7208
There were no -1 votes.
Please find the release at:
/pull/1295
This was then merged into DC/OS 1.9.0-rc2 which passed another suite of
integration tests. Available for testing at
https://dcos.io/releases/1.9.0-rc2/
On Thu, Mar 2, 2017 at 12:02 AM, Adam Bordelon <a...@mesosphere.io> wrote:
> TL;DR: No consensus yet. Let's extend the vote
1)&&(!ubuntu-eu2)/>
> >
> > On Wed, Mar 1, 2017 at 9:24 AM, Greg Mann <g...@mesosphere.io> wrote:
> >
> >> I wanted to give a heads up on a flaky test failure I've encountered
> while
&
Dear Mesos developers and users,
Please vote on releasing the following candidate as Apache Mesos 1.2.0.
1.2.0 includes the following:
* [MESOS-5931] - **Experimental** Support auto backend in Mesos
Containerizer,
sos 1.2,0
> ?
>
> 发件人: Adam Bordelon <a...@mesosphere.io>
> 答复: "user@mesos.apache.org" <user@mesos.apache.org>
> 日期: 2017年2月10日 星期五 上午9:56
> 至: dev <d...@mesos.apache.org>, "user@mesos.apache.org" <
> user@mesos.apache.org>
> 主题: Re: Meso
auth.[NEEDS DOCS]
- Distributed HTTP(S) and TCP Health Checks [has docs]
- Authz for Agent v1 Operator API [NEEDS DOCS?]
- Teardown unregistered frameworks [NEEDS DOCS?]
Please let me know if I've missed something.
On Thu, Feb 2, 2017 at 2:24 PM, Adam Bordelon <a...@mesosphere.io> wrote:
&
+1 binding
Tests passed against DC/OS 1.8.8 (prerelease), which is based on the Apache
Mesos 1.0.x branch.
https://github.com/dcos/dcos/pull/1210
On Wed, Feb 1, 2017 at 10:01 AM, Vinod Kone wrote:
> +1 (binding)
>
> Tested on ASF CI
>
>
> *Revision*:
to 1.3.
Release dashboard: https://issues.apache.org/jira
/secure/Dashboard.jspa?selectPageId=12329897
On Fri, Jan 27, 2017 at 3:45 AM, Adam Bordelon <a...@mesosphere.io> wrote:
> Mesos 1.2.0 status update:
> - 5 blockers
> <https://issues.apache.org/jira/issues/?jql=filter%20%3
ing JIRAs, and
c) *documenting
your new features.*
Release dashboard:
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329897
On Mon, Dec 26, 2016 at 7:04 PM, Adam Bordelon <a...@mesosphere.io> wrote:
> It's about time for Mesos 1.2.0, given our two-month release cadence. I
It's about time for Mesos 1.2.0, given our two-month release cadence. I
volunteer to be release manager, and I'd like to get a new committer or two
to help out. Any volunteers?
I expect to cut rc1 in early January, once all Blockers (and most Critical
issues) have been resolved/deferred. Here's
I don't like the idea of 2) bypassing the 72 hour voting period, so I'd
suggest either we:
1a) ask Yan to cancel his -1 so we can cut 1.0.0 today and blog about it,
then cut 1.0.1 soon after with this and other fixes.
1b) cut an rc5 now and the blogs posted tomorrow mention the rc rather than
an
> Thus I’m trying to run a framework scheduler on a Mesos slave node. I
that possible?
Absolutely. Marathon, Aurora, Singularity, and other "meta-frameworks" can
be used to launch other framework schedulers as Mesos tasks on agent nodes.
There's no reason you can't do the same thing for your own
Shakeel, if you're running a lot of short-lived frameworks/tasks on your
cluster, then your completed tasks may have fallen out of the master's
circular buffer. The master cannot (and should not) store all completed
tasks in memory, so we have configurable limits on how many a master will
keep in
FYI, I made an alternate 1.0 release dashboard with a longer timeframe for
the created vs. resolved chart, and added a couple of my favorite widgets.
Feel free to use anything you find helpful.
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12328256
On Thu, May 26, 2016 at
Backported to 0.28.x and 0.27.x. The relevant change/typo wasn't introduced
until 0.27.x, so I left 0.26.x alone.
On Fri, Apr 29, 2016 at 9:57 AM, Vinod Kone wrote:
> Adam, since you committed this, feel free to backport it to the relevant
> stable branches (26.x, 27.x,
Seems like you're trying to start Marathon with multiple Mesos roles
"spark;sparkr;ms;qa", but Marathon may be interpreting this as a single
role that happens to include semi-colons. Mesos does not yet support
multiple roles in a single framework. See
at 13:37, June Taylor <j...@umn.edu> wrote:
> > Adam,
> >
> > Is there a way to keep this history?
> >
> >
> > Thanks,
> > June Taylor
> > System Administrator, Minnesota Population Center
> > University of Minnesota
> >
> > On Wed,
joint to the other 2.
> I get the problem i described after 10 seconds i get failed to connect,
> but the election of new one works fine because the new leader is 0.27 which
> is stable.
> How to send to you logs?
>
> 2016-04-13 23:53 GMT+02:00 Adam Bordelon <a...@mesosphere.
See also my answer to
http://stackoverflow.com/questions/26597521/can-mesos-master-and-slave-nodes-be-deployed-on-the-same-machines
On Wed, Apr 13, 2016 at 12:45 PM, Stefano Bianchi
wrote:
> I have set an HA cluster.
> 3 mesos slaves with one leader and quorum 2.
> 3
gt; Best,
>> Kapil
>>
>> On Tue, Apr 12, 2016 at 12:22 PM, Steven Borrelli <st...@borrelli.org>
>> wrote:
>>>
>>> I’d be willing to assist in the effort to have standard packages (and
>>> additional packages for modules like net-modules).
pache Mesos project should build and distribute packages
>>> instead of relying on the generosity of a commercial vendor. The Apache
>>> Aurora project does this already with good success. As a user of Apache
>>> Mesos I don't care about Mesosphere Inc and I feel uncomfo
Hi Kamil,
Technically, there are no "official" Apache-built packages for Apache Mesos.
At least once company (Mesosphere) chooses to build and distribute
Mesos packages, but does not currently offer SSL builds. It wouldn't
be hard to add an SSL build to our regular builds, but it hasn't been
I suspect that after your maintenance operation, Marathon may have
registered with a new frameworkId and launched is own copies of your tasks
(why you see double). However, the old Marathon frameworkId probably has a
failover_timeout of a week, so it will continue to be considered
"registered",
Currently, changing any --attributes or --resources requires draining the
agent and killing all running tasks.
See https://issues.apache.org/jira/browse/MESOS-1739
You could do a `mesos-slave --recovery=cleanup` which essentially kills all
the tasks and clears the work_dir; then restart with a
Haosdent, I think Apache mail may strip out images, so you'll have to send
a link to the QR image.
On Sun, Feb 7, 2016 at 8:02 AM, haosdent wrote:
> Hi, our dear Chinese friends. Because some interesting things related to
> China Network, it is a bit difficult to
Den, the other option is to run Mesos on top of OpenShift, and then launch
a new k8s-mesos instance on top of Mesos. You wouldn't be reusing the
existing k8s installation, but you could get Mesos and K8s to share
resources better.
On Mon, Jan 4, 2016 at 11:54 PM, Den Cowboy
You should never specify a quorum of 0.
For 1 master, you specify quorum of 1.
For 3 masters, quorum is 2.
For 5 masters, quorum is 3.
For 7 masters, quorum is 4.
The quorum dictates how many masters (log replicas) have to agree on a fact
to win a vote. If you have a quorum of 0, then no masters
See also:
https://issues.apache.org/jira/browse/MESOS-2258 - Enable filtering of task
information in master/state.json
https://issues.apache.org/jira/browse/MESOS-2353 - Improve performance of
the state.json endpoint for large clusters.
https://issues.apache.org/jira/browse/MESOS-2157 - Add
First off, if we're going to have a /reservations endpoint, we should
follow the same PUT+DELETE pattern for reserve+unreserve, instead of
POST+PUT. And we should consider converting /create and /destroy to
PUT+DELETE verbs on a /volumes endpoint.
Secondly, we're going to have to support the
Please do not skip versions during upgrades. We have been using a
two-version deprecation cycle, so a protobuf field that existed in 0.22.1
may no longer exist in 0.24.x, meaning that a direct live upgrade could
cause masters and agents to stop communicating with each other. We only
guarantee live
Welcome, Kapil! Well-deserved.
On Thu, Nov 5, 2015 at 2:07 AM, haosdent wrote:
> Congratulations!
>
> On Thu, Nov 5, 2015 at 6:02 PM, Till Toenshoff wrote:
>
>> I'm happy to announce that Kapil Arya has been voted a Mesos committer
>> and PMC member!
>>
>>
to the agenda or ask in IRC and I will relay them for you.
On Wed, Nov 4, 2015 at 4:42 PM, Adam Bordelon <a...@mesosphere.io> wrote:
> Sounds great! Please join us at Mesosphere HQ, 88 Stevenson St., SF at 3pm
> Pacific tomorrow.
> We will use youtube-onair again, links to be posted to IR
te between
9pm/9am. Let's get these on the calendar officially.
Vinod, are you/Twitter still planning to host the community sync tomorrow?
On Wed, Oct 14, 2015 at 1:01 AM, Adam Bordelon <a...@mesosphere.io> wrote:
> We'll have the next community sync this Thursday (Oct. 15th) fr
e first Thursday". After
>> this, the other meetings (third Thursday, or every other week?) can
>> alternate between 9pm/9am. Let's get these on the calendar officially.
>>
>> Vinod, are you/Twitter still planning to host the community sync
>> tomorrow?
>>
>>
> When restartng the masters, should they be restarted gradually (restart a
master, wait 30 seconds, restart the next)?
Craig, ideally you should roll the masters one at a time (maintain a
--quorum of masters up at all times), providing enough time for a new
master to recover the replicated log
here.io>
> wrote:
>
>> Hi Paul,
>>
>> I can refer you to the talk given by Adam Bordelon at MesosCon
>> https://www.youtube.com/watch?v=G3sn1OLYDOE
>>
>> If you want to the short answer, the solution is to put a firewall around
>> your cluster.
>&
Hi all,
The vote for Mesos 0.21.2 (rc1) has passed with the following votes.
+1 (Binding)
--
Adam B
Vinod Kone
Michael Park
Niklas Nielsen
There were no 0 or -1 votes.
Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/0.21.2
It is
Hi all,
The vote for Mesos 0.22.2 (rc1) has passed with the following votes.
+1 (Binding)
--
Adam B
Brenden Matthews
Benjamin Mahler
+1 (Non-binding)
--
haosdent
There were no 0 or -1 votes.
Please find the release at:
+1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04.
On Thu, Sep 24, 2015 at 12:10 AM, Adam Bordelon <a...@mesosphere.io> wrote:
> Hi friends,
>
> Here's another docker patch release candidate for you! Please vote on
> releasing the following candidate as A
you also add a tag 0.22.2-rc1
> <https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.22.2-rc1>
> in
> github?
>
> On Thu, Sep 24, 2015 at 4:50 PM, Adam Bordelon <a...@mesosphere.io> wrote:
>
>> +1 (binding) Tested on CI for CentOS7,
including docker
> tests.
>
> On Wed, Sep 23, 2015 at 10:41 PM, Adam Bordelon <a...@mesosphere.io>
> wrote:
>
> > +1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04.
> >
> > On Tue, Sep 22, 2015 at 1:41 PM, Niklas Nielsen <nik...@mesosphere.i
Hi friends,
Here's a candidate for the last of the docker patch releases
(0.21.x-0.24.x).
Please vote on releasing the following candidate as Apache Mesos 0.21.2.
0.21.2 is a bug fix release and includes the following:
;> +1 (non binding)
> >>
> >> Tested Ubuntu 14.04, OSX
> >>
> >> > On 22 Sep 2015, at 03:06, Adam Bordelon <a...@mesosphere.io> wrote:
> >> >
> >> > Hi friends,
>
+1 (binding) Tested on CI for CentOS7 and Ubuntu 14.04.
On Thu, Sep 24, 2015 at 5:44 PM, Adam Bordelon <a...@mesosphere.io> wrote:
> Hi friends,
>
> Here's a candidate for the last of the docker patch releases
> (0.21.x-0.24.x).
> Please vote on releasing the following cand
;> Tested on CI for CentOS5 and CentOS6.
>>
>> On Fri, Sep 18, 2015 at 6:21 PM, Adam Bordelon <a...@mesosphere.io>
>> wrote:
>>
>>> Hi friends,
>>>
>>> Please vote
+1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04.
On Wed, Sep 23, 2015 at 10:25 AM, haosdent <haosd...@gmail.com> wrote:
> +1 test on Ubuntu 14.04
>
> On Tue, Sep 22, 2015 at 9:06 AM, Adam Bordelon <a...@mesosphere.io> wrote:
>
>> Hi friends,
FYI, the default executor will claim 32MB of RAM, so you'll either need to
use a custom executor and specify less RAM, or pretend that your slaves
have way more memory than they actually do.
On Mon, Sep 21, 2015 at 11:11 AM, Joris Van Remoortere
wrote:
> > I launched tasks
Hi friends,
Please vote on releasing the following candidate as Apache Mesos 0.23.1.
0.23.1 is a bug fix release and includes the following:
* [MESOS-2986] - Docker version output is not compatible with Mesos
*
Hi friends,
Please vote on releasing the following candidate as Apache Mesos 0.24.1.
0.24.1 includes the following:
* [MESOS-2986] - Docker version output is not compatible with Mesos
* [MESOS-3136] - COMMAND health
is Van Remoortere <jo...@mesosphere.io>
wrote:
> Youtube on-air: http://youtu.be/ZQT6-fw8Ito
> Speakers channel:
> https://plus.google.com/hangouts/_/hoaevent/AP36tYd59qP_P4ac-NwOI7LztI_hBsku54gXqk1DhFGsKkne_cmByA
>
> On Mon, Sep 14, 2015 at 7:02 PM, Adam Bordelon <a...@mesosph
r: The Mesos Community Developer Sync will be happening today at
>>> 3pm Pacific.
>>>
>>> To participate remotely, join the Google hangout:
>>> https://plus.google.com/hangouts/_/twitter.com/mesos-sync
>>>
>>> On Thu, Jun 18, 2015 at 7:22 AM,
Egg publishing is a part of the formal release process. It is listed under
"Update external tooling" at the end of the release guide.
http://mesos.apache.org/documentation/latest/release-guide/
I think we're still working on finishing up this release. Even
mesos.apache.org hasn't been updated yet.
I've added your MUG to
https://svn.apache.org/repos/asf/mesos/site/source/community/user-groups.html.md
and it will show up on the website on the next update.
On Sun, Aug 23, 2015 at 6:00 PM, Walsh, Ed ed.wa...@emc.com wrote:
I am organizing an Apache Mesos user group in the NY Capital region
Greetings, friends.
I'm adam-mesos, and I'm a Distributed Systems Architect at Mesosphere and
an Apache Mesos committer. My current areas of focus are security
https://mesoscon2015.sched.org/event/7c88ed02112a47935292554102f6d25a,
storage, and stateful services
Andrii, you might also be interested in the new
--executor_environment_variables flag on the slave.
See http://mesos.apache.org/documentation/latest/configuration/
I'm not sure if this override occurs before the docker run command.
On Mon, Aug 3, 2015 at 8:51 AM, Timothy Chen t...@mesosphere.io
Spark should be setting the FrameworkInfo.webui_url on scheduler startup.
https://github.com/apache/spark/blob/v1.4.1/core/src/main/scala/org/apache/spark/deploy/mesos/MesosClusterDispatcher.scala#L76
What versions of Mesos and Spark are you using?
On Tue, Jul 28, 2015 at 3:40 PM, Philip Weaver
0. How do i go about the issue of HA at the scheduler level?
One alternative to having to do your own leader election is to use a
meta-framework like Marathon or Aurora to automatically restart your
scheduler. There will be a short downtime during the failover, but as soon
as the new scheduler
A simple nginx reverse proxy will get you most of the way there, but only
for the master webui. Since the tasks' sandboxes are hosted on each slave's
webui, you would also have to reverse proxy each slave's webui in order for
sandboxes to be publicly accessible. More complicated, but not
, at 4:43 PM, Adam Bordelon a...@mesosphere.io
wrote:
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos
0.23.0.
0.23.0 includes the following:
- Per
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
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.0.
0.23.0 includes the following:
- Per-container network isolation
- Dockerized slaves will properly recover Docker
deciding votes by 6pm Pacific today, I'll extend the
vote for another day.
On Thu, Jul 9, 2015 at 6:09 PM, Khanduja, Vaibhav vaibhav.khand...@emc.com
wrote:
+1
Sent from my iPhone. Please excuse the typos and brevity of this message.
On Jul 9, 2015, at 6:07 PM, Adam Bordelon
of
'required'. That's an API change, which would be nice to go into 0.23.0
as
well.
So, not a -1 per se, but if you are willing to cut another RC, I can
land
the fixes today. Sorry for the trouble.
On Thu, Jul 16, 2015 at 11:48 AM, Adam Bordelon a...@mesosphere.io
wrote:
+1 (binding
it a blocker.
Can't update the spreadsheet. So here are the commits I would like
cherry-picked.
fc85cc512b7767fc2e3921b15cf6602c0c68593e
bfe6c07b79550bb3d1f2ab6f5344d740e6eb6f60
Thanks Adam.
On Thu, Jul 16, 2015 at 7:39 PM, Adam Bordelon a...@mesosphere.io
wrote:
The 7 day voting period
Reusing taskIds may work if you're guaranteed to never be running two
instances of the same taskId simultaneously, but I could imagine a
particularly dangerous scenario where a master and slave experience a
network partition, so the master declares the slave lost and therefore its
tasks lost, and
...@mesosphere.io
wrote:
Reminder: The Mesos Community Developer Sync will be happening today at
3pm Pacific.
To participate remotely, join the Google hangout:
https://plus.google.com/hangouts/_/twitter.com/mesos-sync
On Thu, Jun 18, 2015 at 7:22 AM, Adam Bordelon a...@mesosphere.io wrote
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.0.
0.23.0 includes the following:
- Per-container network isolation
- Dockerized slaves will properly recover Docker
Release Candidate 2 did not pass, due to MESOS-3025.
I just cut rc3 and opened the vote (in a separate thread).
On Thu, Jul 9, 2015 at 5:20 PM, Ian Downes idow...@twitter.com wrote:
No it doesn't block me (I normally compile without python...).
On Thu, Jul 9, 2015 at 4:48 PM, Adam Bordelon
provide pointers as to how to run
hdfs-mesos using marathon ?
-Bhargav
On Sun, Jul 5, 2015 at 10:53 PM, Adam Bordelon a...@mesosphere.io wrote:
Kk,
There are two options for running the hdfs framework on Mesos.
- If you already have the hadoop/hdfs binaries on all your nodes, you can
follow
on an ImportError for mesos.native
See here for more details:
https://gist.github.com/SEJeff/05a31c1d2d10fecc97a1
On Wednesday, July 8, 2015, Adam Bordelon a...@mesosphere.io wrote:
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.
0.
0.23.0 includes
Python package isn't part of make check.
It pops on an ImportError for mesos.native
See here for more details:
https://gist.github.com/SEJeff/05a31c1d2d10fecc97a1
On Wednesday, July 8, 2015, Adam Bordelon a...@mesosphere.io
wrote:
Hello Mesos community,
Please vote on releasing
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.0.
0.23.0 includes the following:
- Per-container network isolation
- Dockerized slaves will properly recover Docker
PM, Adam Bordelon a...@mesosphere.io wrote:
In case it wasn't obvious, rc1 did not pass the vote, due to a few build
and unit test issues.
Most of those fixes have been committed, so we will cut rc2 when the last
blocker is resolved.
This is your last chance to get any recently committed
Sorry for showing up late to the party. Good answers so far. I just want to
add that if you know any master, you can hit
http://somemaster/master/redirect
to get a 307 Temporary Redirect which you can unpack to find the leading
master's hostname:port.
On Wed, Jul 8, 2015 at 10:59 AM, Nikolaos
*
*Distributed Systems Engineer*
On Fri, Jul 3, 2015 at 12:25 PM, Adam Bordelon a...@mesosphere.io
wrote:
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos
0.23.0.
0.23.0 includes the following
?selectPageId=12326227
On Tue, Jul 7, 2015 at 1:59 PM, Adam Bordelon a...@mesosphere.io wrote:
-1 (non-binding) Network isolator will not compile.
https://issues.apache.org/jira/browse/MESOS-3002
The changes for MESOS-2800
https://issues.apache.org/jira/browse/MESOS-2800 to Rename
OptionT::get
Kk,
There are two options for running the hdfs framework on Mesos.
- If you already have the hadoop/hdfs binaries on all your nodes, you can
follow the instructions in
https://github.com/mesosphere/hdfs#if-you-have-hadoop-pre-installed-in-your-cluster
to tell the scheduler to use the preinstalled
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.0.
0.23.0 includes the following:
- Per-container network isolation
- Upgraded minimum required compilers to GCC 4.8+ or
See Master::exited()
https://github.com/apache/mesos/blob/0.22.1/src/master/master.cpp#L878
which derives from Process::exited()
https://github.com/apache/mesos/blob/0.22.1/3rdparty/libprocess/include/process/process.hpp#L55
In the event of a temporary network partition, the Mesos master will
/_/mesosphere.io/mesos-developer
On Mon, Jun 15, 2015 at 10:46 AM, Adam Bordelon a...@mesosphere.io wrote:
As previously mentioned, we would like to host additional Mesos developer
syncs at our new Mesosphere HQ at 88 Stevenson St (tucked behind Market
2nd), starting this Thursday from 9-11am
Thanks,
-Adam-
On Thu, May 28, 2015 at 10:08 AM, Vinod Kone vinodk...@gmail.com wrote:
Cool.
Here's the agenda doc
https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#
for next week that folks can fill in.
On Thu, May 28, 2015 at 9:52 AM, Adam Bordelon
4. By default, Mesos will not revoke (rescind) an *un*used offer being
held by a framework, but you can enable such a timeout by specifying the
`--offer_timeout` flag on the master.
On Thu, Jun 11, 2015 at 4:48 PM, Adam Bordelon a...@mesosphere.io wrote:
1. The modularized allocator will still
The allocator is currently only pluggable insomuch as it is a C++ class,
and one could subclass/replace it with a custom implementation and then
recompile Mesos. The default/only allocator implementation is
(hierarchical) DRF, which will only offer a resource to a single framework
at a time.
True
Wow, what a response! Allow me to attempt to summarize the sentiment so far.
Let's start with the implicit question,
*0. Should we rename Mesos Slave?*
+1 (Explicit approval) 12, including 7 from JIRA
+0.5 (Implicit approval, suggested alternate name) 18
-0.5 (Some disapproval, wouldn't block it)
[] Master-Follower
[] Mesos-Follower
[] Master-worker
[] Mesos-worker
[] etc etc
-
Tally the result and go from there.
James
On 06/05/2015 04:27 AM, Adam Bordelon wrote:
Wow, what a response! Allow me to attempt to summarize the sentiment so
far.
Let's start
1 - 100 of 169 matches
Mail list logo