[RESULT][VOTE] Release Apache Mesos 0.28.3 (rc1)

2016-12-05 Thread Anand Mazumdar 
Hi all,

The vote for Mesos 0.28.3 (rc1) has passed with the
following votes.

+1 (Binding)
--
Alex Rukletsov
Vinod Kone
Benjamin Mahler

+1 (Non-binding)
--
Greg Mann

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/0.28.3

It is recommended to use a mirror to download the release:
http://www.apache.org/dyn/closer.cgi

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.28.3

The mesos-0.28.3.jar has been released to:
https://repository.apache.org

The website (http://mesos.apache.org) will be updated shortly to reflect
this release.

Thanks,
Anand & Joseph

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

2016-12-01 Thread Benjamin Mahler 
+1 (binding)

On Wed, Nov 30, 2016 at 2:53 PM, Greg Mann  wrote:

> +1 (non-binding)
>
> Did `sudo make check` on CentOS 7. Aside from several
> LinuxFilesystemIsolatorTests and two other flaky
> tests, CgroupsAnyHierarchyWithFreezerTest.ROOT_CGROUPS_
> DestroyTracedProcess
> and MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery, everything passed.
>
> Cheers,
> Greg
>
> On Wed, Nov 30, 2016 at 5:53 AM, Alex Rukletsov 
> wrote:
>
> > Joseph—
> >
> > Thank you for investigating. I'm
> > +1 (binding)
> > make check passes on CentOS 7, Fedora 23, Ubuntu 14, 15 modulo known
> flaky
> > tests, including LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem.
> >
> > On 29 Nov 2016 21:21, "Joseph Wu"  wrote:
> >
> >> AlexR,
> >>
> >> Thanks for pointing out those test failures.  As of 0.28, the
> >> LinuxFilesystemIsolatorTests were notoriously flaky on distributions
> with
> >> "large" root filesystems.  The test would essentially copy the root
> >> filesystem, leading to timeouts in multiple places in the tests.
> CentOS 7
> >> was known to have at least twice as much stuff to copy compared to the
> >> other distributions (not sure about Fedora 23).
> >>
> >> Looking at your logs (and logs you didn't attach), we see that a couple
> >> of the tests that exercise the same code path did in fact pass, while
> >> others timed out.  I wouldn't consider that a regression.
> >>
> >> On Mon, Nov 28, 2016 at 12:54 PM, Vinod Kone 
> >> wrote:
> >>
> >>> +1 (binding)
> >>>
> >>> Tested on ASF CI.
> >>>
> >>>
> >>> *Revision*: 52a0b0a41482da35dc736ec2fd445b6099e7a4e7
> >>>
> >>>- refs/tags/0.28.3-rc1
> >>>
> >>> Configuration Matrix gcc clang
> >>> centos:7 --verbose --enable-libevent --enable-ssl autotools
> >>> [image: Success]
> >>>  Release/25/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >>> [image: Not run]
> >>> cmake
> >>> [image: Success]
> >>>  Release/25/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%
> 7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >>> [image: Not run]
> >>> --verbose autotools
> >>> [image: Success]
> >>>  Release/25/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_
> exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >>> [image: Not run]
> >>> cmake
> >>> [image: Success]
> >>>  Release/25/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%
> 3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >>> [image: Not run]
> >>> ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
> >>> [image: Success]
> >>>  Release/25/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >>> [image: Success]
> >>>  Release/25/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >>> cmake
> >>> [image: Success]
> >>>  Release/25/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >>> [image: Success]
> >>>  Release/25/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=-
> -verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >>> --verbose autotools
> >>> [image: Success]
> >>>  Release/25/BUILDTOOL=autotools,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]
> >>>  Release/25/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose,
>

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

2016-11-28 Thread Alex Rukletsov 
I see LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem failing on
CentOS 7 and Fedora 23, see e.g., [1]. I don't see any backports touching
[2], can it be a regression or this test is know to be problematic in
0.28.x?

[1] http://pastebin.com/c5PzfGF8
[2]
https://github.com/apache/mesos/blob/0.28.x/src/tests/containerizer/filesystem_isolator_tests.cpp

On Thu, Nov 24, 2016 at 12:07 AM, Anand Mazumdar  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.28.3.
>
>
> 0.28.3 includes the following:
> 
> 
>
> ** Bug
>   * [MESOS-2043] - Framework auth fail with timeout error and never
> get authenticated
>   * [MESOS-4638] - Versioning preprocessor macros.
>   * [MESOS-5073] - Mesos allocator leaks role sorter and quota role
> sorters.
>   * [MESOS-5330] - Agent should backoff before connecting to the master.
>   * [MESOS-5390] - v1 Executor Protos not included in maven jar
>   * [MESOS-5543] - /dev/fd is missing in the Mesos containerizer
> environment.
>   * [MESOS-5571] - Scheduler JNI throws exception when the major
> versions of JAR and libmesos don't match.
>   * [MESOS-5576] - Masters may drop the first message they send
> between masters after a network partition.
>   * [MESOS-5673] - Port mapping isolator may cause segfault if it bind
> mount root does not exist.
>   * [MESOS-5691] - SSL downgrade support will leak sockets in CLOSE_WAIT
> status.
>   * [MESOS-5698] - Quota sorter not updated for resource changes at agent.
>   * [MESOS-5723] - SSL-enabled libprocess will leak incoming links to
> forks.
>   * [MESOS-5740] - Consider adding `relink` functionality to libprocess.
>   * [MESOS-5748] - Potential segfault in `link` when linking to a
> remote process.
>   * [MESOS-5763] - Task stuck in fetching is not cleaned up after
> --executor_registration_timeout.
>   * [MESOS-5913] - Stale socket FD usage when using libevent + SSL.
>   * [MESOS-5927] - Unable to run "scratch" Dockerfiles with Unified
> Containerizer.
>   * [MESOS-5943] - Incremental http parsing of URLs leads to decoder error.
>   * [MESOS-5986] - SSL Socket CHECK can fail after socket receives EOF.
>   * [MESOS-6104] - Potential FD double close in libevent's
> implementation of `sendfile`.
>   * [MESOS-6142] - Frameworks may RESERVE for an arbitrary role.
>   * [MESOS-6152] - Resource leak in libevent_ssl_socket.cpp.
>   * [MESOS-6233] - Master CHECK fails during recovery while relinking
> to other masters.
>   * [MESOS-6234] - Potential socket leak during Zookeeper network changes.
>   * [MESOS-6246] - Libprocess links will not generate an ExitedEvent
> if the socket creation fails.
>   * [MESOS-6299] - Master doesn't remove task from pending when it is
> invalid.
>   * [MESOS-6457] - Tasks shouldn't transition from TASK_KILLING to
> TASK_RUNNING.
>   * [MESOS-6502] - _version uses incorrect
> MESOS_{MAJOR,MINOR,PATCH}_VERSION in libmesos java binding.
>   * [MESOS-6527] - Memory leak in the libprocess request decoder.
>   * [MESOS-6621] - SSL downgrade path will CHECK-fail when using both
> temporary and persistent sockets
>
>
> 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.28.3-rc1
> 
> 
>
> The candidate for Mesos 0.28.3 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/0.28.3-rc1/
> mesos-0.28.3.tar.gz
>
> The tag to be voted on is 0.28.3-rc1:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.28.3-rc1
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/0.28.3-rc1/
> mesos-0.28.3.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/0.28.3-rc1/
> mesos-0.28.3.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-1170
>
> Please vote on releasing this package as Apache Mesos 0.28.3!
>
> The vote is open until Sat Nov 26 14:59:10 PST 2016 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.28.3
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Anand & Joseph
>

[VOTE] Release Apache Mesos 0.28.3 (rc1)

2016-11-23 Thread Anand Mazumdar 
Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.28.3.


0.28.3 includes the following:


** Bug
  * [MESOS-2043] - Framework auth fail with timeout error and never
get authenticated
  * [MESOS-4638] - Versioning preprocessor macros.
  * [MESOS-5073] - Mesos allocator leaks role sorter and quota role sorters.
  * [MESOS-5330] - Agent should backoff before connecting to the master.
  * [MESOS-5390] - v1 Executor Protos not included in maven jar
  * [MESOS-5543] - /dev/fd is missing in the Mesos containerizer environment.
  * [MESOS-5571] - Scheduler JNI throws exception when the major
versions of JAR and libmesos don't match.
  * [MESOS-5576] - Masters may drop the first message they send
between masters after a network partition.
  * [MESOS-5673] - Port mapping isolator may cause segfault if it bind
mount root does not exist.
  * [MESOS-5691] - SSL downgrade support will leak sockets in CLOSE_WAIT status.
  * [MESOS-5698] - Quota sorter not updated for resource changes at agent.
  * [MESOS-5723] - SSL-enabled libprocess will leak incoming links to forks.
  * [MESOS-5740] - Consider adding `relink` functionality to libprocess.
  * [MESOS-5748] - Potential segfault in `link` when linking to a
remote process.
  * [MESOS-5763] - Task stuck in fetching is not cleaned up after
--executor_registration_timeout.
  * [MESOS-5913] - Stale socket FD usage when using libevent + SSL.
  * [MESOS-5927] - Unable to run "scratch" Dockerfiles with Unified
Containerizer.
  * [MESOS-5943] - Incremental http parsing of URLs leads to decoder error.
  * [MESOS-5986] - SSL Socket CHECK can fail after socket receives EOF.
  * [MESOS-6104] - Potential FD double close in libevent's
implementation of `sendfile`.
  * [MESOS-6142] - Frameworks may RESERVE for an arbitrary role.
  * [MESOS-6152] - Resource leak in libevent_ssl_socket.cpp.
  * [MESOS-6233] - Master CHECK fails during recovery while relinking
to other masters.
  * [MESOS-6234] - Potential socket leak during Zookeeper network changes.
  * [MESOS-6246] - Libprocess links will not generate an ExitedEvent
if the socket creation fails.
  * [MESOS-6299] - Master doesn't remove task from pending when it is invalid.
  * [MESOS-6457] - Tasks shouldn't transition from TASK_KILLING to TASK_RUNNING.
  * [MESOS-6502] - _version uses incorrect
MESOS_{MAJOR,MINOR,PATCH}_VERSION in libmesos java binding.
  * [MESOS-6527] - Memory leak in the libprocess request decoder.
  * [MESOS-6621] - SSL downgrade path will CHECK-fail when using both
temporary and persistent sockets


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.28.3-rc1


The candidate for Mesos 0.28.3 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.28.3-rc1/mesos-0.28.3.tar.gz

The tag to be voted on is 0.28.3-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.28.3-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.28.3-rc1/mesos-0.28.3.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.28.3-rc1/mesos-0.28.3.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-1170

Please vote on releasing this package as Apache Mesos 0.28.3!

The vote is open until Sat Nov 26 14:59:10 PST 2016 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.28.3
[ ] -1 Do not release this package because ...

Thanks,
Anand & Joseph