Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

2016-03-01 Thread Kevin Klues 
-1 (non-binding)

This release
​candidate ​
should have included the backport to re
​s​
olv
​e ​
MESOS-4518 ​.
​All ​of the other release candidates that came out as backports recently
have included this, but somehow this one was overlooked.




On Tue, Mar 1, 2016 at 4:35 PM, Greg Mann  wrote:

> I was able to successfully test a simple upgrade scenario between
> 0.26.1-rc1 and 0.27.2-rc1 using Niklas's upgrade testing script, which I've
> modified slightly and reposted here: https://reviews.apache.org/r/44229/
>
> On Tue, Mar 1, 2016 at 2:22 PM, Kevin Klues  wrote:
>
> > The others all seem to have them though:
> >
> >
> >
> https://github.com/apache/mesos/commits/0.26.1-rc1/src/tests/master_tests.cpp
> >
> >
> https://github.com/apache/mesos/commits/0.25.1-rc1/src/tests/master_tests.cpp
> >
> >
> https://github.com/apache/mesos/commits/0.24.2-rc1/src/tests/master_tests.cpp
> >
> > Just not:
> >
> >
> https://github.com/apache/mesos/commits/0.27.2-rc1/src/tests/master_tests.cpp
> >
> > On Tue, Mar 1, 2016 at 2:17 PM, Kevin Klues  wrote:
> > > Looks like this rc is missing this commit:
> > >
> > >
> >
> https://github.com/apache/mesos/commit/d3108d776b6f7121e37176eda686ecc7245be4cd
> > >
> > > On Tue, Mar 1, 2016 at 2:08 PM, Joris Van Remoortere
> > >  wrote:
> > >> @Michael Browning:
> > >>>
> > >>> MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in
> > >>> MESOS-4518]
> > >>
> > >> This is supposed to be fixed in this release. It is concerning that
> this
> > >> came up.
> > >> Can you verify this and provide logs to Kevin Klues?
> > >>
> > >>
> > >> —
> > >> Joris Van Remoortere
> > >> Mesosphere
> > >>
> > >> On Tue, Mar 1, 2016 at 2:00 PM, Michael Browning <
> > invitapri...@gmail.com>
> > >> wrote:
> > >>>
> > >>> +1 (non-binding)
> > >>>
> > >>> Fedora 23: `make check` non-root OK
> > >>> OS X: `make check` non-root OK
> > >>> Ubuntu 14.04: `make check` non-root, three failures:
> > >>> ContainerLoggerTest.DefaultToSandbox [flaky, tracked in MESOS-4615]
> > >>> MasterQuotaTest.AvailableResourcesAfterRescinding [flaky, tracked in
> > >>> MESOS-4542]
> > >>> MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in
> > >>> MESOS-4518]
> > >>>
> > >>> On Mon, Feb 29, 2016 at 10:40 PM, Greg Mann 
> > wrote:
> > >>>
> > >>> > +1 (non-binding)
> > >>> >
> > >>> > `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL
> > >>> > enabled.
> > >>> >
> > >>> > All tests pass except
> > MemoryPressureMesosTest.CGROUPS_ROOT_Statistics,
> > >>> > which seems to be due to the issue found here:
> > >>> > https://issues.apache.org/jira/browse/MESOS-4053
> > >>> >
> > >>> >
> > >>> > On Mon, Feb 29, 2016 at 2:17 PM, Michael Park 
> > wrote:
> > >>> >
> > >>> > > Vinod, we've only committed the CHANGELOGs to the specific tags.
> I
> > >>> > > didn't
> > >>> > > realize that I should commit those to master as well, but it
> makes
> > >>> > > total
> > >>> > > sense to do so. I'll do that. Thanks.
> > >>> > >
> > >>> > > On 29 February 2016 at 13:50, Vinod Kone 
> > wrote:
> > >>> > >
> > >>> > >> I don't see CHANGELOGs for these versions on the master branch?
> > >>> > >>
> > >>> > >> On Mon, Feb 29, 2016 at 1:39 PM, Neil Conway <
> > neil.con...@gmail.com>
> > >>> > >> wrote:
> > >>> > >>
> > >>> > >> > As described (briefly) in the release emails, 0.27.2, 0.26.1,
> > >>> > >> > 0.25.1,
> > >>> > >> > and 0.24.2 contains a new feature: "reliable floating point
> for
> > >>> > >> > scalar
> > >>> > >> > resources" (MESOS-4687).
> > >>> > >> >
> > >>> > >> > To elaborate on that slightly, Mesos now only supports scalar
> > >>> > >> > resource
> > >>> > >> > values with three decimal digits of precision (e.g., reserving
> > >>> > >> > "5.001
> > >>> > >> > CPUs" for a task). As a result of this change, frameworks that
> > do
> > >>> > >> > their own resource math may see slightly different results;
> > >>> > >> > furthermore, if any frameworks were trying to manage extremely
> > >>> > >> > fine-grained resource values (> 3 decimal digits of
> precision),
> > >>> > >> > that
> > >>> > >> > will no longer be supported.
> > >>> > >> >
> > >>> > >> > For more information, please see:
> > >>> > >> >
> > >>> > >> >
> > >>> > >> >
> > >>> > >>
> > >>> >
> > >>> >
> >
> https://mail-archives.apache.org/mod_mbox/mesos-user/201602.mbox/%3CCAOW5sYZJn5caBOwZyPV008JgL1F2FYFxL_bM5CtYA2PF2OG7Bw%40mail.gmail.com%3E
> > >>> > >> >
> > >>> > >> >
> > >>> > >>
> > >>> >
> > >>> >
> >
> https://docs.google.com/document/d/14qLxjZsfIpfynbx0USLJR0GELSq8hdZJUWw6kaY_DXc/edit?usp=sharing
> > >>> > >> > https://issues.apache.org/jira/browse/MESOS-4687
> > >>> > >> >
> > >>> > >> > Neil
> > >>> > >> >
> > >>> > >> >
> > >>> > >> > On Fri, Feb 26, 2016 at 8:54 PM, Michael Park <
> > mcyp...@gmail.com>
> > >>> > >> wrote:
> > >>> >

marathon-lb at scale

2016-03-01 Thread Bill Green 
For folks using marathon-lb, how far have you scaled it? I’d be very interested 
to hear your experiences with it, especially in the area of partition tolerance.

Any insights would be greatly appreciated, thanks!

--
Bill Green
SRE, New Relic
@cloudangst

Re: Asking for Help: Destroy docker container from marathon kills mesos slave

2016-03-01 Thread zhz shi 
No we don't run mesos-slave in docker, it's managed by systemd, we launch
all tasks in Docker.

The problem is that we cann't repro it, it just happened from time to time
on our production. I've created an issue at
https://issues.apache.org/jira/browse/MESOS-4827.

Thanks.

On Wed, Mar 2, 2016 at 9:48 AM, Tim Chen  wrote:

> Not in particularly, I remember seeing something similiar in the past when
> Mesos slave itself is launched in a Docker container, but in your case I
> don't think you guys are doing that.
>
> Does it repro 100% of the time? If you create a ticket with repro steps we
> can take a look.
>
> Tim
>
> On Tue, Mar 1, 2016 at 5:41 PM, zhz shi  wrote:
>
>> Yes we have a plan to do the upgrade but do you know the root cause of
>> this problem for 0.25?
>>
>> On Wed, Mar 2, 2016 at 1:49 AM, Tim Chen  wrote:
>>
>>> Are you able to try out the latest Mesos release instead of 0.25?
>>>
>>> Tim
>>>
>>> On Mon, Feb 29, 2016 at 9:11 PM, shizhz  wrote:
>>>
 Hi all,

 Is this the correct place to ask for help? If it is could anybody help
 me on the problem I posted on SOF:
 http://stackoverflow.com/questions/35713985/destroy-docker-container-from-marathon-kills-mesos-slave
 .

 Sorry for bothering and wish you all have a nice day.

 BR, Shizhz

>>>
>>>
>>
>>
>> --
>> BR, Zhenzhong
>>
>
>


-- 
BR, Zhenzhong

Re: Asking for Help: Destroy docker container from marathon kills mesos slave

2016-03-01 Thread Tim Chen 
Not in particularly, I remember seeing something similiar in the past when
Mesos slave itself is launched in a Docker container, but in your case I
don't think you guys are doing that.

Does it repro 100% of the time? If you create a ticket with repro steps we
can take a look.

Tim

On Tue, Mar 1, 2016 at 5:41 PM, zhz shi  wrote:

> Yes we have a plan to do the upgrade but do you know the root cause of
> this problem for 0.25?
>
> On Wed, Mar 2, 2016 at 1:49 AM, Tim Chen  wrote:
>
>> Are you able to try out the latest Mesos release instead of 0.25?
>>
>> Tim
>>
>> On Mon, Feb 29, 2016 at 9:11 PM, shizhz  wrote:
>>
>>> Hi all,
>>>
>>> Is this the correct place to ask for help? If it is could anybody help
>>> me on the problem I posted on SOF:
>>> http://stackoverflow.com/questions/35713985/destroy-docker-container-from-marathon-kills-mesos-slave
>>> .
>>>
>>> Sorry for bothering and wish you all have a nice day.
>>>
>>> BR, Shizhz
>>>
>>
>>
>
>
> --
> BR, Zhenzhong
>

Re: Asking for Help: Destroy docker container from marathon kills mesos slave

2016-03-01 Thread zhz shi 
Yes we have a plan to do the upgrade but do you know the root cause of this
problem for 0.25?

On Wed, Mar 2, 2016 at 1:49 AM, Tim Chen  wrote:

> Are you able to try out the latest Mesos release instead of 0.25?
>
> Tim
>
> On Mon, Feb 29, 2016 at 9:11 PM, shizhz  wrote:
>
>> Hi all,
>>
>> Is this the correct place to ask for help? If it is could anybody help me
>> on the problem I posted on SOF:
>> http://stackoverflow.com/questions/35713985/destroy-docker-container-from-marathon-kills-mesos-slave
>> .
>>
>> Sorry for bothering and wish you all have a nice day.
>>
>> BR, Shizhz
>>
>
>


-- 
BR, Zhenzhong

Re: [VOTE] Release Apache Mesos 0.26.1 (rc1)

2016-03-01 Thread Kevin Klues 
I committed a fix for this in:
https://github.com/apache/mesos/commit/42f746937233349660c687ea7a66cc0a78871663

Looks like that's post 0.26 though, so maybe it should be included in the
.1 rc

On Mon, Feb 29, 2016 at 2:27 PM, Vinod Kone  wrote:

> Looks like the ASF CI builds for CentOS7 are failing because they are
> unable to find JAVA_HOME. Couldn't tell if it's an issue with the docker
> build script or something in the configure script.
>
>
> checking for svn_txdelta in -lsvn_delta-1... yes
> checking for sasl_done in -lsasl2... yes
> checking SASL CRAM-MD5 support... yes
> checking for javac... /usr/bin/javac
> checking for java... /usr/bin/java
> checking value of Java system property 'java.home'... 
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.71-2.b15.el7_2.x86_64/jre
> configure: error: could not guess JAVA_HOME
>
>
>
> *Revision*: a05261dbed1c2577676b11235380de95d586aeeb
>
>- refs/tags/0.26.1-rc1
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl
> [image: Failed]
> 
> [image: Not run]
> --verbose
> [image: Failed]
> 
> [image: Not run]
> ubuntu:14.04 --verbose --enable-libevent --enable-ssl
> [image: Success]
> 
> [image: Success]
> 
> --verbose
> [image: Success]
> 
> [image: Success]
> 
>
> On Mon, Feb 29, 2016 at 11:21 AM, Kapil Arya  wrote:
>
>> +1 (binding)
>>
>> Successful CI builds for the following distros:
>>
>> amd64/centos/6
>> amd64/centos/7
>> amd64/debian/jessie
>> amd64/ubuntu/precise
>> amd64/ubuntu/trusty
>> amd64/ubuntu/vivid
>>
>> Kapil
>>
>> On Sat, Feb 27, 2016 at 12:26 AM, Michael Park  wrote:
>>
>> > Hi all,
>> >
>> > Please vote on releasing the following candidate as Apache Mesos 0.26.1.
>> >
>> >
>> > 0.26.1 includes the following:
>> >
>> >
>> 
>> >
>> >- Improvements
>> >   - `/state` endpoint performance
>> >   - systemd integration
>> >   - GLOG performance
>> >   - Configurable task/framework history
>> >   - Offer filter timeout fix for backlogged allocator
>> >
>> >
>> >- Bugs
>> >- SSL
>> >   - Libevent
>> >   - Fixed point resources math
>> >- HDFS
>> >   - Agent upgrade compatibility
>> >
>> > 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=0.26.1-rc1
>> >
>> >
>> 
>> >
>> > The candidate for Mesos 0.26.1 release is available at:
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc1/mesos-0.26.1.tar.gz
>> >
>> > The tag to be voted on is 0.26.1-rc1:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.1-rc1
>> >
>> > The MD5 checksum of the tarball can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc1/mesos-0.26.1.tar.gz.md5
>> >
>> > The signature of the tarball can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc1/mesos-0.26.1.tar.gz.asc
>> >
>> > The PGP key used to sign the release is here:
>> > https://dist.apache.org/repos/dist/release/mesos/KEYS
>> >
>> > The JAR is up in Maven in a staging repository here:
>> > https://repository.apache.org/content/repositories/orgapachemesos-1106
>> >
>> > Please vote on releasing this package as Apache Mesos 0.26.1!
>> >
>> > The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a
>> majority
>> > of at least 3 +1 PMC votes are cast.
>> >
>> > [ ] +1 Release this package as Apache Mesos 0.26.1
>> > [ ] -1 Do not release this package because ...
>> >
>> > Thanks,
>> >
>> > Joris, Kapil, MPark
>> >
>>
>
>


-- 
~Kevin

Re: [VOTE] Release Apache Mesos 0.26.1 (rc1)

2016-03-01 Thread Greg Mann 
I was also able to successfully test a simple upgrade scenario between
0.25.1-rc1 and 0.26.1-rc1 using Niklas's upgrade testing script, which I've
modified slightly and reposted here: https://reviews.apache.org/r/44229/

On Mon, Feb 29, 2016 at 10:31 PM, Greg Mann  wrote:

> +1 (non-binding)
>
> `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL enabled.
>
> All tests pass except:
>
> PerfEventIsolatorTest.ROOT_CGROUPS_Sample, which is covered here:
> https://issues.apache.org/jira/browse/MESOS-4655
>
> CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf,
> MemoryPressureMesosTest.CGROUPS_ROOT_Statistics, and
> MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery, due to the issue here:
> https://issues.apache.org/jira/browse/MESOS-3215
>
> On Mon, Feb 29, 2016 at 2:27 PM, Vinod Kone  wrote:
>
>> Looks like the ASF CI builds for CentOS7 are failing because they are
>> unable to find JAVA_HOME. Couldn't tell if it's an issue with the docker
>> build script or something in the configure script.
>>
>>
>> checking for svn_txdelta in -lsvn_delta-1... yes
>> checking for sasl_done in -lsasl2... yes
>> checking SASL CRAM-MD5 support... yes
>> checking for javac... /usr/bin/javac
>> checking for java... /usr/bin/java
>> checking value of Java system property 'java.home'... 
>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.71-2.b15.el7_2.x86_64/jre
>> configure: error: could not guess JAVA_HOME
>>
>>
>>
>> *Revision*: a05261dbed1c2577676b11235380de95d586aeeb
>>
>>- refs/tags/0.26.1-rc1
>>
>> Configuration Matrix gcc clang
>> centos:7 --verbose --enable-libevent --enable-ssl
>> [image: Failed]
>> 
>> [image: Not run]
>> --verbose
>> [image: Failed]
>> 
>> [image: Not run]
>> ubuntu:14.04 --verbose --enable-libevent --enable-ssl
>> [image: Success]
>> 
>> [image: Success]
>> 
>> --verbose
>> [image: Success]
>> 
>> [image: Success]
>> 
>>
>> On Mon, Feb 29, 2016 at 11:21 AM, Kapil Arya  wrote:
>>
>>> +1 (binding)
>>>
>>> Successful CI builds for the following distros:
>>>
>>> amd64/centos/6
>>> amd64/centos/7
>>> amd64/debian/jessie
>>> amd64/ubuntu/precise
>>> amd64/ubuntu/trusty
>>> amd64/ubuntu/vivid
>>>
>>> Kapil
>>>
>>> On Sat, Feb 27, 2016 at 12:26 AM, Michael Park  wrote:
>>>
>>> > Hi all,
>>> >
>>> > Please vote on releasing the following candidate as Apache Mesos
>>> 0.26.1.
>>> >
>>> >
>>> > 0.26.1 includes the following:
>>> >
>>> >
>>> 
>>> >
>>> >- Improvements
>>> >   - `/state` endpoint performance
>>> >   - systemd integration
>>> >   - GLOG performance
>>> >   - Configurable task/framework history
>>> >   - Offer filter timeout fix for backlogged allocator
>>> >
>>> >
>>> >- Bugs
>>> >- SSL
>>> >   - Libevent
>>> >   - Fixed point resources math
>>> >- HDFS
>>> >   - Agent upgrade compatibility
>>> >
>>> > 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=0.26.1-rc1
>>> >
>>> >
>>> 
>>> >
>>> > The candidate for Mesos 0.26.1 release is available at:
>>> >
>>> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc1/mesos-0.26.1.tar.gz
>>> >
>>> > The tag to be voted on is 0.26.1-rc1:
>>> >
>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.1-rc1
>>> >
>>> > The MD5 checksum of the tarball can be found at:
>>> >
>>> >
>>> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc1/mesos-0.26.1.tar.gz.md5
>>> >
>>> > The signature of the tarball can be found at:
>>> >
>>> >
>>> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc1/mesos-0.26.1.tar.gz.asc
>>> >
>>> > The PGP key used to sign the release

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

2016-03-01 Thread Greg Mann 
I was able to successfully test a simple upgrade scenario between
0.26.1-rc1 and 0.27.2-rc1 using Niklas's upgrade testing script, which I've
modified slightly and reposted here: https://reviews.apache.org/r/44229/

On Tue, Mar 1, 2016 at 2:22 PM, Kevin Klues  wrote:

> The others all seem to have them though:
>
>
> https://github.com/apache/mesos/commits/0.26.1-rc1/src/tests/master_tests.cpp
>
> https://github.com/apache/mesos/commits/0.25.1-rc1/src/tests/master_tests.cpp
>
> https://github.com/apache/mesos/commits/0.24.2-rc1/src/tests/master_tests.cpp
>
> Just not:
>
> https://github.com/apache/mesos/commits/0.27.2-rc1/src/tests/master_tests.cpp
>
> On Tue, Mar 1, 2016 at 2:17 PM, Kevin Klues  wrote:
> > Looks like this rc is missing this commit:
> >
> >
> https://github.com/apache/mesos/commit/d3108d776b6f7121e37176eda686ecc7245be4cd
> >
> > On Tue, Mar 1, 2016 at 2:08 PM, Joris Van Remoortere
> >  wrote:
> >> @Michael Browning:
> >>>
> >>> MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in
> >>> MESOS-4518]
> >>
> >> This is supposed to be fixed in this release. It is concerning that this
> >> came up.
> >> Can you verify this and provide logs to Kevin Klues?
> >>
> >>
> >> —
> >> Joris Van Remoortere
> >> Mesosphere
> >>
> >> On Tue, Mar 1, 2016 at 2:00 PM, Michael Browning <
> invitapri...@gmail.com>
> >> wrote:
> >>>
> >>> +1 (non-binding)
> >>>
> >>> Fedora 23: `make check` non-root OK
> >>> OS X: `make check` non-root OK
> >>> Ubuntu 14.04: `make check` non-root, three failures:
> >>> ContainerLoggerTest.DefaultToSandbox [flaky, tracked in MESOS-4615]
> >>> MasterQuotaTest.AvailableResourcesAfterRescinding [flaky, tracked in
> >>> MESOS-4542]
> >>> MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in
> >>> MESOS-4518]
> >>>
> >>> On Mon, Feb 29, 2016 at 10:40 PM, Greg Mann 
> wrote:
> >>>
> >>> > +1 (non-binding)
> >>> >
> >>> > `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL
> >>> > enabled.
> >>> >
> >>> > All tests pass except
> MemoryPressureMesosTest.CGROUPS_ROOT_Statistics,
> >>> > which seems to be due to the issue found here:
> >>> > https://issues.apache.org/jira/browse/MESOS-4053
> >>> >
> >>> >
> >>> > On Mon, Feb 29, 2016 at 2:17 PM, Michael Park 
> wrote:
> >>> >
> >>> > > Vinod, we've only committed the CHANGELOGs to the specific tags. I
> >>> > > didn't
> >>> > > realize that I should commit those to master as well, but it makes
> >>> > > total
> >>> > > sense to do so. I'll do that. Thanks.
> >>> > >
> >>> > > On 29 February 2016 at 13:50, Vinod Kone 
> wrote:
> >>> > >
> >>> > >> I don't see CHANGELOGs for these versions on the master branch?
> >>> > >>
> >>> > >> On Mon, Feb 29, 2016 at 1:39 PM, Neil Conway <
> neil.con...@gmail.com>
> >>> > >> wrote:
> >>> > >>
> >>> > >> > As described (briefly) in the release emails, 0.27.2, 0.26.1,
> >>> > >> > 0.25.1,
> >>> > >> > and 0.24.2 contains a new feature: "reliable floating point for
> >>> > >> > scalar
> >>> > >> > resources" (MESOS-4687).
> >>> > >> >
> >>> > >> > To elaborate on that slightly, Mesos now only supports scalar
> >>> > >> > resource
> >>> > >> > values with three decimal digits of precision (e.g., reserving
> >>> > >> > "5.001
> >>> > >> > CPUs" for a task). As a result of this change, frameworks that
> do
> >>> > >> > their own resource math may see slightly different results;
> >>> > >> > furthermore, if any frameworks were trying to manage extremely
> >>> > >> > fine-grained resource values (> 3 decimal digits of precision),
> >>> > >> > that
> >>> > >> > will no longer be supported.
> >>> > >> >
> >>> > >> > For more information, please see:
> >>> > >> >
> >>> > >> >
> >>> > >> >
> >>> > >>
> >>> >
> >>> >
> https://mail-archives.apache.org/mod_mbox/mesos-user/201602.mbox/%3CCAOW5sYZJn5caBOwZyPV008JgL1F2FYFxL_bM5CtYA2PF2OG7Bw%40mail.gmail.com%3E
> >>> > >> >
> >>> > >> >
> >>> > >>
> >>> >
> >>> >
> https://docs.google.com/document/d/14qLxjZsfIpfynbx0USLJR0GELSq8hdZJUWw6kaY_DXc/edit?usp=sharing
> >>> > >> > https://issues.apache.org/jira/browse/MESOS-4687
> >>> > >> >
> >>> > >> > Neil
> >>> > >> >
> >>> > >> >
> >>> > >> > On Fri, Feb 26, 2016 at 8:54 PM, Michael Park <
> mcyp...@gmail.com>
> >>> > >> wrote:
> >>> > >> > > Hi all,
> >>> > >> > >
> >>> > >> > > Please vote on releasing the following candidate as Apache
> Mesos
> >>> > >> 0.27.2.
> >>> > >> > >
> >>> > >> > >
> >>> > >> > > 0.27.2 includes the following:
> >>> > >> > >
> >>> > >> >
> >>> > >>
> >>> >
> >>> >
> 
> >>> > >> > >
> >>> > >> > > MESOS-4693 - Variable shadowing in
> >>> > >> HookManager::slavePreLaunchDockerHook.
> >>> > >> > > MESOS-4711 - Race condition in libevent poll implementation
> >>> > >> > > causes
> >>> > >> crash.
> >>> > >> > > MESOS-4754 - The "executors" field is exposed under a
>

Re: [VOTE] Release Apache Mesos 0.25.1 (rc1)

2016-03-01 Thread Greg Mann 
I was also able to successfully test a simple upgrade scenario between
0.24.2-rc1 and 0.25.1-rc1 using Niklas's upgrade testing script, which I've
modified slightly and reposted here: https://reviews.apache.org/r/44229/

On Tue, Mar 1, 2016 at 9:29 AM, Greg Mann  wrote:

> +1 (non-binding)
>
> `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL enabled.
>
> All tests pass except:
>
> PerfEventIsolatorTest.ROOT_CGROUPS_Sample, which is covered here:
> https://issues.apache.org/jira/browse/MESOS-4655
>
> CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf,
> MemoryPressureMesosTest.CGROUPS_ROOT_Statistics, and
> MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery, due to the issue here:
> https://issues.apache.org/jira/browse/MESOS-3215
>
> Cheers,
> Greg
>
>
> On Mon, Feb 29, 2016 at 11:21 AM, Kapil Arya  wrote:
>
>> +1 (binding)
>>
>> Successful CI builds for the following distros:
>>
>> amd64/centos/6
>> amd64/centos/7
>> amd64/debian/jessie
>> amd64/ubuntu/precise
>> amd64/ubuntu/trusty
>> amd64/ubuntu/vivid
>>
>> Kapil
>>
>> On Sat, Feb 27, 2016 at 12:53 AM, Michael Park  wrote:
>>
>> > Hi all,
>> >
>> > Please vote on releasing the following candidate as Apache Mesos 0.25.1.
>> >
>> >
>> > 0.25.1 includes the following:
>> >
>> >
>> 
>> >
>> >- Improvements
>> >   - `/state` endpoint performance
>> >   - systemd integration
>> >   - GLOG performance
>> >   - Configurable task/framework history
>> >   - Offer filter timeout fix for backlogged allocator
>> >
>> >
>> >- Bugs
>> >- SSL
>> >   - Libevent
>> >   - Fixed point resources math
>> >- HDFS
>> >   - Agent upgrade compatibility
>> >   - Health checks
>> >
>> > 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=0.25.1-rc1
>> >
>> >
>> 
>> >
>> > The candidate for Mesos 0.25.1 release is available at:
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz
>> >
>> > The tag to be voted on is 0.25.1-rc1:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.1-rc1
>> >
>> > The MD5 checksum of the tarball can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz.md5
>> >
>> > The signature of the tarball can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz.asc
>> >
>> > The PGP key used to sign the release is here:
>> > https://dist.apache.org/repos/dist/release/mesos/KEYS
>> >
>> > The JAR is up in Maven in a staging repository here:
>> > https://repository.apache.org/content/repositories/orgapachemesos-1108
>> >
>> > Please vote on releasing this package as Apache Mesos 0.25.1!
>> >
>> > The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a
>> majority
>> > of at least 3 +1 PMC votes are cast.
>> >
>> > [ ] +1 Release this package as Apache Mesos 0.25.1
>> > [ ] -1 Do not release this package because ...
>> >
>> > Thanks,
>> >
>> > Joris, Kapil, MPark
>> >
>>
>
>

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

2016-03-01 Thread Kevin Klues 
Looks like this rc is missing this commit:

https://github.com/apache/mesos/commit/d3108d776b6f7121e37176eda686ecc7245be4cd

On Tue, Mar 1, 2016 at 2:08 PM, Joris Van Remoortere
 wrote:
> @Michael Browning:
>>
>> MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in
>> MESOS-4518]
>
> This is supposed to be fixed in this release. It is concerning that this
> came up.
> Can you verify this and provide logs to Kevin Klues?
>
>
> —
> Joris Van Remoortere
> Mesosphere
>
> On Tue, Mar 1, 2016 at 2:00 PM, Michael Browning 
> wrote:
>>
>> +1 (non-binding)
>>
>> Fedora 23: `make check` non-root OK
>> OS X: `make check` non-root OK
>> Ubuntu 14.04: `make check` non-root, three failures:
>> ContainerLoggerTest.DefaultToSandbox [flaky, tracked in MESOS-4615]
>> MasterQuotaTest.AvailableResourcesAfterRescinding [flaky, tracked in
>> MESOS-4542]
>> MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in
>> MESOS-4518]
>>
>> On Mon, Feb 29, 2016 at 10:40 PM, Greg Mann  wrote:
>>
>> > +1 (non-binding)
>> >
>> > `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL
>> > enabled.
>> >
>> > All tests pass except MemoryPressureMesosTest.CGROUPS_ROOT_Statistics,
>> > which seems to be due to the issue found here:
>> > https://issues.apache.org/jira/browse/MESOS-4053
>> >
>> >
>> > On Mon, Feb 29, 2016 at 2:17 PM, Michael Park  wrote:
>> >
>> > > Vinod, we've only committed the CHANGELOGs to the specific tags. I
>> > > didn't
>> > > realize that I should commit those to master as well, but it makes
>> > > total
>> > > sense to do so. I'll do that. Thanks.
>> > >
>> > > On 29 February 2016 at 13:50, Vinod Kone  wrote:
>> > >
>> > >> I don't see CHANGELOGs for these versions on the master branch?
>> > >>
>> > >> On Mon, Feb 29, 2016 at 1:39 PM, Neil Conway 
>> > >> wrote:
>> > >>
>> > >> > As described (briefly) in the release emails, 0.27.2, 0.26.1,
>> > >> > 0.25.1,
>> > >> > and 0.24.2 contains a new feature: "reliable floating point for
>> > >> > scalar
>> > >> > resources" (MESOS-4687).
>> > >> >
>> > >> > To elaborate on that slightly, Mesos now only supports scalar
>> > >> > resource
>> > >> > values with three decimal digits of precision (e.g., reserving
>> > >> > "5.001
>> > >> > CPUs" for a task). As a result of this change, frameworks that do
>> > >> > their own resource math may see slightly different results;
>> > >> > furthermore, if any frameworks were trying to manage extremely
>> > >> > fine-grained resource values (> 3 decimal digits of precision),
>> > >> > that
>> > >> > will no longer be supported.
>> > >> >
>> > >> > For more information, please see:
>> > >> >
>> > >> >
>> > >> >
>> > >>
>> >
>> > https://mail-archives.apache.org/mod_mbox/mesos-user/201602.mbox/%3CCAOW5sYZJn5caBOwZyPV008JgL1F2FYFxL_bM5CtYA2PF2OG7Bw%40mail.gmail.com%3E
>> > >> >
>> > >> >
>> > >>
>> >
>> > https://docs.google.com/document/d/14qLxjZsfIpfynbx0USLJR0GELSq8hdZJUWw6kaY_DXc/edit?usp=sharing
>> > >> > https://issues.apache.org/jira/browse/MESOS-4687
>> > >> >
>> > >> > Neil
>> > >> >
>> > >> >
>> > >> > On Fri, Feb 26, 2016 at 8:54 PM, Michael Park 
>> > >> wrote:
>> > >> > > Hi all,
>> > >> > >
>> > >> > > Please vote on releasing the following candidate as Apache Mesos
>> > >> 0.27.2.
>> > >> > >
>> > >> > >
>> > >> > > 0.27.2 includes the following:
>> > >> > >
>> > >> >
>> > >>
>> >
>> > 
>> > >> > >
>> > >> > > MESOS-4693 - Variable shadowing in
>> > >> HookManager::slavePreLaunchDockerHook.
>> > >> > > MESOS-4711 - Race condition in libevent poll implementation
>> > >> > > causes
>> > >> crash.
>> > >> > > MESOS-4754 - The "executors" field is exposed under a backwards
>> > >> > incompatible
>> > >> > > schema.
>> > >> > > MESOS-4687 - Implement reliable floating point for scalar
>> > >> > > resources.
>> > >> > >
>> > >> > >
>> > >> > > 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=0.27.2-rc1
>> > >> > >
>> > >> >
>> > >>
>> >
>> > 
>> > >> > >
>> > >> > > The candidate for Mesos 0.27.2 release is available at:
>> > >> > >
>> > >> >
>> > >>
>> >
>> > https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz
>> > >> > >
>> > >> > > The tag to be voted on is 0.27.2-rc1:
>> > >> > >
>> > >> >
>> > >>
>> >
>> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.27.2-rc1
>> > >> > >
>> > >> > > The MD5 checksum of the tarball can be found at:
>> > >> > >
>> > >> >
>> > >>
>> >
>> > https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz.md5
>> > >> > >
>> > >> > > The signature of the tarball can be found at:
>> > >> > >
>> >

Re: Multicast blocked?

2016-03-01 Thread Avinash Sridharan 
Hi David,
 Is your discovery service part of the Executor ? Some more context of the
interaction of the Executor and the discovery service would be helpful. If
the discovery service is relying specifically on multicast, and you no the
packet payload for the discovery messages, might help to run tcpdump on the
NIC to see if the messages are going out when you start your executor.

Thanks,
Avinash

On Tue, Mar 1, 2016 at 1:40 PM, David Wood  wrote:

> I'm building an Executor that uses a separate discovery service that
> relies on multicast.  If I run the executor without calling
> MesosExecutorDriver.run() the executor discovers other (non-mesos) nodes in
> my distributed set up just fine.  But if I call run(), then it does not
> discover the other nodes.  Interestingly, the other  nodes can discover my
> executor regardless of whether run() is called or not.   My executor is a
> Java app started using a command line task.  Any help is much appreciated.
>
>
> David Wood
> Computing Systems for Wireless Networks
> IBM TJ Watson Research Center
> daw...@us.ibm.com
> 914-945-4923 (office), 914-396-6515 (mobile)
>



-- 
Avinash Sridharan, Mesosphere
+1 (323) 702 5245

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

2016-03-01 Thread Joris Van Remoortere 
@Michael Browning:
>
> MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in
> MESOS-4518]

This is supposed to be fixed in this release. It is concerning that this
came up.
Can you verify this and provide logs to Kevin Klues?


—
*Joris Van Remoortere*
Mesosphere

On Tue, Mar 1, 2016 at 2:00 PM, Michael Browning 
wrote:

> +1 (non-binding)
>
> Fedora 23: `make check` non-root OK
> OS X: `make check` non-root OK
> Ubuntu 14.04: `make check` non-root, three failures:
> ContainerLoggerTest.DefaultToSandbox [flaky, tracked in MESOS-4615]
> MasterQuotaTest.AvailableResourcesAfterRescinding [flaky, tracked in
> MESOS-4542]
> MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in MESOS-4518]
>
> On Mon, Feb 29, 2016 at 10:40 PM, Greg Mann  wrote:
>
> > +1 (non-binding)
> >
> > `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL
> enabled.
> >
> > All tests pass except MemoryPressureMesosTest.CGROUPS_ROOT_Statistics,
> > which seems to be due to the issue found here:
> > https://issues.apache.org/jira/browse/MESOS-4053
> >
> >
> > On Mon, Feb 29, 2016 at 2:17 PM, Michael Park  wrote:
> >
> > > Vinod, we've only committed the CHANGELOGs to the specific tags. I
> didn't
> > > realize that I should commit those to master as well, but it makes
> total
> > > sense to do so. I'll do that. Thanks.
> > >
> > > On 29 February 2016 at 13:50, Vinod Kone  wrote:
> > >
> > >> I don't see CHANGELOGs for these versions on the master branch?
> > >>
> > >> On Mon, Feb 29, 2016 at 1:39 PM, Neil Conway 
> > >> wrote:
> > >>
> > >> > As described (briefly) in the release emails, 0.27.2, 0.26.1,
> 0.25.1,
> > >> > and 0.24.2 contains a new feature: "reliable floating point for
> scalar
> > >> > resources" (MESOS-4687).
> > >> >
> > >> > To elaborate on that slightly, Mesos now only supports scalar
> resource
> > >> > values with three decimal digits of precision (e.g., reserving
> "5.001
> > >> > CPUs" for a task). As a result of this change, frameworks that do
> > >> > their own resource math may see slightly different results;
> > >> > furthermore, if any frameworks were trying to manage extremely
> > >> > fine-grained resource values (> 3 decimal digits of precision), that
> > >> > will no longer be supported.
> > >> >
> > >> > For more information, please see:
> > >> >
> > >> >
> > >> >
> > >>
> >
> https://mail-archives.apache.org/mod_mbox/mesos-user/201602.mbox/%3CCAOW5sYZJn5caBOwZyPV008JgL1F2FYFxL_bM5CtYA2PF2OG7Bw%40mail.gmail.com%3E
> > >> >
> > >> >
> > >>
> >
> https://docs.google.com/document/d/14qLxjZsfIpfynbx0USLJR0GELSq8hdZJUWw6kaY_DXc/edit?usp=sharing
> > >> > https://issues.apache.org/jira/browse/MESOS-4687
> > >> >
> > >> > Neil
> > >> >
> > >> >
> > >> > On Fri, Feb 26, 2016 at 8:54 PM, Michael Park 
> > >> wrote:
> > >> > > Hi all,
> > >> > >
> > >> > > Please vote on releasing the following candidate as Apache Mesos
> > >> 0.27.2.
> > >> > >
> > >> > >
> > >> > > 0.27.2 includes the following:
> > >> > >
> > >> >
> > >>
> >
> 
> > >> > >
> > >> > > MESOS-4693 - Variable shadowing in
> > >> HookManager::slavePreLaunchDockerHook.
> > >> > > MESOS-4711 - Race condition in libevent poll implementation causes
> > >> crash.
> > >> > > MESOS-4754 - The "executors" field is exposed under a backwards
> > >> > incompatible
> > >> > > schema.
> > >> > > MESOS-4687 - Implement reliable floating point for scalar
> resources.
> > >> > >
> > >> > >
> > >> > > 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=0.27.2-rc1
> > >> > >
> > >> >
> > >>
> >
> 
> > >> > >
> > >> > > The candidate for Mesos 0.27.2 release is available at:
> > >> > >
> > >> >
> > >>
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz
> > >> > >
> > >> > > The tag to be voted on is 0.27.2-rc1:
> > >> > >
> > >> >
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.27.2-rc1
> > >> > >
> > >> > > The MD5 checksum of the tarball can be found at:
> > >> > >
> > >> >
> > >>
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz.md5
> > >> > >
> > >> > > The signature of the tarball can be found at:
> > >> > >
> > >> >
> > >>
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz.asc
> > >> > >
> > >> > > The PGP key used to sign the release is here:
> > >> > > https://dist.apache.org/repos/dist/release/mesos/KEYS
> > >> > >
> > >> > > The JAR is up in Maven in a staging repository here:
> > >> > >
> > >>
> https://repository.apache.org/content/repositories/orgapachemesos-1104
> > >> > >
> > >> > > Please vote on releasing this

Multicast blocked?

2016-03-01 Thread David Wood 
I'm building an Executor that uses a separate discovery service that 
relies on multicast.  If I run the executor without calling 
MesosExecutorDriver.run() the executor discovers other (non-mesos) nodes 
in my distributed set up just fine.  But if I call run(), then it does not 
discover the other nodes.  Interestingly, the other  nodes can discover my 
executor regardless of whether run() is called or not.   My executor is a 
Java app started using a command line task.  Any help is much appreciated. 
 


David Wood 
Computing Systems for Wireless Networks
IBM TJ Watson Research Center
daw...@us.ibm.com
914-945-4923 (office), 914-396-6515 (mobile)

Re: Asking for Help: Destroy docker container from marathon kills mesos slave

2016-03-01 Thread Tim Chen 
Are you able to try out the latest Mesos release instead of 0.25?

Tim

On Mon, Feb 29, 2016 at 9:11 PM, shizhz  wrote:

> Hi all,
>
> Is this the correct place to ask for help? If it is could anybody help me
> on the problem I posted on SOF:
> http://stackoverflow.com/questions/35713985/destroy-docker-container-from-marathon-kills-mesos-slave
> .
>
> Sorry for bothering and wish you all have a nice day.
>
> BR, Shizhz
>

Re: [VOTE] Release Apache Mesos 0.25.1 (rc1)

2016-03-01 Thread Greg Mann 
+1 (non-binding)

`sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL enabled.

All tests pass except:

PerfEventIsolatorTest.ROOT_CGROUPS_Sample, which is covered here:
https://issues.apache.org/jira/browse/MESOS-4655

CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf,
MemoryPressureMesosTest.CGROUPS_ROOT_Statistics, and
MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery, due to the issue here:
https://issues.apache.org/jira/browse/MESOS-3215

Cheers,
Greg


On Mon, Feb 29, 2016 at 11:21 AM, Kapil Arya  wrote:

> +1 (binding)
>
> Successful CI builds for the following distros:
>
> amd64/centos/6
> amd64/centos/7
> amd64/debian/jessie
> amd64/ubuntu/precise
> amd64/ubuntu/trusty
> amd64/ubuntu/vivid
>
> Kapil
>
> On Sat, Feb 27, 2016 at 12:53 AM, Michael Park  wrote:
>
> > Hi all,
> >
> > Please vote on releasing the following candidate as Apache Mesos 0.25.1.
> >
> >
> > 0.25.1 includes the following:
> >
> >
> 
> >
> >- Improvements
> >   - `/state` endpoint performance
> >   - systemd integration
> >   - GLOG performance
> >   - Configurable task/framework history
> >   - Offer filter timeout fix for backlogged allocator
> >
> >
> >- Bugs
> >- SSL
> >   - Libevent
> >   - Fixed point resources math
> >- HDFS
> >   - Agent upgrade compatibility
> >   - Health checks
> >
> > 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=0.25.1-rc1
> >
> >
> 
> >
> > The candidate for Mesos 0.25.1 release is available at:
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz
> >
> > The tag to be voted on is 0.25.1-rc1:
> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.1-rc1
> >
> > The MD5 checksum of the tarball can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz.md5
> >
> > The signature of the tarball can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz.asc
> >
> > The PGP key used to sign the release is here:
> > https://dist.apache.org/repos/dist/release/mesos/KEYS
> >
> > The JAR is up in Maven in a staging repository here:
> > https://repository.apache.org/content/repositories/orgapachemesos-1108
> >
> > Please vote on releasing this package as Apache Mesos 0.25.1!
> >
> > The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a
> majority
> > of at least 3 +1 PMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Mesos 0.25.1
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> >
> > Joris, Kapil, MPark
> >
>

Re: How did the mesos master detect the disconnect of a framework (scheduler)

2016-03-01 Thread tommy xiao 
Cool

2016-03-01 2:48 GMT+08:00 Chong Chen :

> Thanks, it is clear and helpful!
>
>
>
> *From:* haosdent [mailto:haosd...@gmail.com]
> *Sent:* Saturday, February 27, 2016 2:28 AM
> *To:* user
> *Subject:* Re: How did the mesos master detect the disconnect of a
> framework (scheduler)
>
>
>
> Joseph's  explanation quite detail.
>
> On Feb 27, 2016 3:33 AM, "Joseph Wu"  wrote:
>
> Here's a brief(?) run-down:
>
>1.
>
> https://github.com/apache/mesos/blob/4376803007446b949840d53945547d8a61b91339/src/master/master.cpp#L5739-L5748
>
> 
>When a new framework is added, the master opens a socket connection
>with the framework.
>
>
>- If this is a scheduler-driver-based framework, this is a plain
>   socket connection.
>   - If this is a new HTTP API framework, the master uses the
>   streaming HTTP connection instead.
>
>
>1. The HTTP API framework's exit logic is simpler to explain.  When
>the streaming connection closes, the master considers the framework to have
>exited.  In the above code, see this chunk of code:
>http.closed()
>  .onAny(defer(self(), ::exited, framework->id(), http));
>2. The scheduler-driver-based framework exit is a bit more involved:
>
>
>1.
>   
> https://github.com/apache/mesos/blob/4376803007446b949840d53945547d8a61b91339/3rdparty/libprocess/src/process.cpp#L1326
>   Libprocess has a SocketManager which, as the name suggests, managed
>   sockets.  Linking the master <-> framework spawns a socket here.
>   2.
>   
> https://github.com/apache/mesos/blob/4376803007446b949840d53945547d8a61b91339/3rdparty/libprocess/src/process.cpp#L1394-L1400
>   Linking will install a dispatch loop, which continually reads the
>   data from the socket until the socket closes.
>   3.
>   
> https://github.com/apache/mesos/blob/4376803007446b949840d53945547d8a61b91339/3rdparty/libprocess/src/process.cpp#L1300-L1312
>   The dispatch loop calls "ignore_recv_data".  This detects when the
>   socket closes and calls "SocketManager->close(s)".
>   4.
>   
> https://github.com/apache/mesos/blob/4376803007446b949840d53945547d8a61b91339/3rdparty/libprocess/src/process.cpp#L1928
>   "SocketManager->close" will generate a libprocess "ExitedEvent".
>   5.
>   
> https://github.com/apache/mesos/blob/4376803007446b949840d53945547d8a61b91339/src/master/master.cpp#L1352
>   Master has a listener for "ExitedEvent" which rate-limits these
>   events.
>   6.
>   
> https://github.com/apache/mesos/blob/4376803007446b949840d53945547d8a61b91339/src/master/master.cpp#L1161
>   The "ExitedEvent" eventually gets propagated to that ^ method
>   (through a libprocess event visitor).
>   7.
>   
> https://github.com/apache/mesos/blob/4376803007446b949840d53945547d8a61b91339/src/master/master.cpp#L1165
>   Finally, the framework gets removed.
>
> Hope that helps,
>
> ~Joseph
>
>
>
> On Fri, Feb 26, 2016 at 10:45 AM, Chong Chen 
> wrote:
>
> Hi,
>
> When a running framework was disconnected (manually terminated), the Mesos
> master will detect it immediately.  The master::exited() function will be
> invoked with log info “framework disconnected”.
>
> I just wondering, how this disconnect detection was implemented in Mesos?
> I can’t find any place in mesos src directory where the Master::exit()
> function was called.
>
>
>
> Thanks!
>
>
>
> Best Regards,
>
> Chong
>
>
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com