+1 (binding) Deployed on a small-ish test cluster for about a week. Monitoring of that test cluster has not caught any problems with Mesos.
Also confirmed that this SSL socket FD leak does not affect Mesos, except in tests: https://issues.apache.org/jira/browse/MESOS-6919 On Mon, Mar 6, 2017 at 9:52 AM, Jie Yu <yujie....@gmail.com> wrote: > -0 > > I wanna fix MESOS-7208 <https://issues.apache.org/jira/browse/MESOS-7208> > which > affects all tasks that are launched as non-root using container image. > > But this is not a new regression because it exists in 1.1.0, thus I am a -0 > > - Jie > > On Fri, Mar 3, 2017 at 4:08 PM, Vinod Kone <vinodk...@apache.org> wrote: > >> +1 (binding) >> >> Since the perf and flaky test that I reported earlier doesn't seem to be >> blockers. >> >> On Fri, Mar 3, 2017 at 4:01 PM, Adam Bordelon <a...@mesosphere.io> wrote: >> >> > I haven't heard any -1's so I'm going to go ahead and vote myself, from a >> > DC/OS perspective: >> > >> > +1 (binding) >> > >> > I ran 1.2.0-rc2 through the DC/OS integration tests on top of the >> > 1.9.0-rc1, which covers many Mesos features and tests multiple >> frameworks. >> > See CI results of https://github.com/dcos/dcos/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 for a day or two, until >> we >> >> have 3 +1s or a legit -1. >> >> During that time we can test further, and investigate any issues that >> >> have shown up. >> >> >> >> Here's a summary of what's been reported on the 1.2.0-rc2 vote thread: >> >> >> >> - There was a perf core dump on ASF CI, which is not necessarily a >> >> blocker: >> >> MESOS-7160 Parsing of perf version segfaults >> >> Perhaps fixed by backporting MESOS-6982: PerfTest.Version fails on >> >> recent Arch Linux >> >> >> >> - There were a couple of (known/unsurprising) flaky tests: >> >> MESOS-7185 DockerRuntimeIsolatorTest.ROOT_INTERNET_CURL_ >> DockerDefaultEntryptRegistryPuller >> >> is flaky >> >> MESOS-4570 DockerFetcherPluginTest.INTERNET_CURL_FetchImage seems >> flaky. >> >> >> >> - If we were to have an rc3, the following Critical bugs could be >> >> included: >> >> MESOS-7050 IOSwitchboard FDs leaked when containerizer launch fails -- >> >> leads to deadlock >> >> MESOS-6982 PerfTest.Version fails on recent Arch Linux >> >> >> >> - Plus doc updates: >> >> MESOS-7188 Add documentation for Debug APIs to Operator API doc >> >> MESOS-7189 Add nested container launch/wait/kill APIs to agent API >> >> docs. >> >> >> >> >> >> On Wed, Mar 1, 2017 at 11:30 AM, Neil Conway <neil.con...@gmail.com> >> >> wrote: >> >> >> >>> The perf core dump might be addressed if we backport this change: >> >>> >> >>> https://reviews.apache.org/r/56611/ >> >>> >> >>> Although my guess is that this isn't a severe problem: for some >> >>> as-yet-unknown reason, running `perf` on the host segfaulted, which >> >>> causes the test to fail. >> >>> >> >>> Neil >> >>> >> >>> On Wed, Mar 1, 2017 at 11:09 AM, Vinod Kone <vinodk...@apache.org> >> >>> wrote: >> >>> > Tested on ASF CI. >> >>> > >> >>> > Saw 2 configurations fail. One was the perf core dump issue >> >>> > <https://issues.apache.org/jira/browse/MESOS-7160>. Other is a known >> >>> (since >> >>> > 0..28.0) flaky test with Docker fetcher plugin >> >>> > <https://issues.apache.org/jira/browse/MESOS-4570>. >> >>> > >> >>> > Withholding the vote until we know the severity of the perf core >> dump. >> >>> > >> >>> > >> >>> > *Revision*: b9d8202a7444d0d1e49476bfc9817eb4583beaff >> >>> > >> >>> > - refs/tags/1.1.1-rc2 >> >>> > >> >>> > Configuration Matrix gcc clang >> >>> > centos:7 --verbose --enable-libevent --enable-ssl autotools >> >>> > [image: Success] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--ver >> >>> bose%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] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/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%7CHadoo >> >>> p)&&(!ubuntu-us1)&&(!ubuntu-eu2)/> >> >>> > [image: Not run] >> >>> > --verbose autotools >> >>> > [image: Success] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--ver >> >>> bose,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] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/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] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--ver >> >>> bose%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: Failed] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/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] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/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%7CH >> >>> adoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/> >> >>> > [image: Success] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbo >> >>> se%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] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--ver >> >>> bose,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-Rel >> >>> ease/30/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=-- >> >>> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A1 >> >>> 4.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/> >> >>> > cmake >> >>> > [image: Success] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose >> >>> ,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,la >> >>> bel_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/> >> >>> > [image: Success] >> >>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >> >>> ease/30/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbo >> >>> se,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04, >> >>> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!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 >> >>> >> testing this RC: 'DockerRuntimeIsolatorTest.ROO >> >>> >> T_INTERNET_CURL_DockerDefaultEntryptRegistryPuller'. One issue >> >>> related to >> >>> >> this test was resolved recently (https://issues.apache.org/ >> >>> >> jira/browse/MESOS-6001), but this seems to be a separate issue ( >> >>> >> https://issues.apache.org/jira/browse/MESOS-7185). I haven't had >> >>> time to >> >>> >> triage yet so I'm not sure if this represents a legitimate bug, but >> I >> >>> >> thought I'd email here to increase visibility while the vote is out. >> >>> >> >> >>> >> Cheers, >> >>> >> Greg >> >>> >> >> >>> >> >> >>> >> On Fri, Feb 24, 2017 at 1:14 AM, Adam Bordelon <a...@mesosphere.io> >> >>> wrote: >> >>> >> >> >>> >> > 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, >> >>> >> > prefering overlayfs then aufs. Please note that the bind >> backend >> >>> >> needs >> >>> >> > to be >> >>> >> > specified explicitly through the agent flag >> >>> >> > '--image_provisioner_backend' >> >>> >> > since it requires the sandbox already existed. >> >>> >> > >> >>> >> > * [MESOS-6402] - **Experimental** Add rlimit support to Mesos >> >>> >> > containerizer. >> >>> >> > The isolator adds support for setting POSIX resource limits >> >>> (rlimits) >> >>> >> > for >> >>> >> > containers launched using the Mesos containerizer. POSIX >> >>> rlimits can >> >>> >> be >> >>> >> > used >> >>> >> > to control the resources a process can consume. See `docs/ >> >>> >> > posix_rlimits.md` >> >>> >> > for details. >> >>> >> > >> >>> >> > * [MESOS-6419] - **Experimental** Teardown unregistered >> >>> frameworks. The >> >>> >> > master >> >>> >> > now treats recovered frameworks very similarly to frameworks >> >>> that are >> >>> >> > registered >> >>> >> > but currently disconnected. For example, recovered frameworks >> >>> will be >> >>> >> > reported >> >>> >> > via the normal "frameworks" key when querying HTTP endpoints. >> >>> This >> >>> >> > means there >> >>> >> > is no longer a concept of "orphan tasks": if the master knows >> >>> about a >> >>> >> > task, the >> >>> >> > task will be running under a framework. Similarly, "teardown" >> >>> >> > operations on >> >>> >> > recovered frameworks will now work correctly. >> >>> >> > >> >>> >> > * [MESOS-6460] - **Experimental** Container Attach and Exec. >> This >> >>> >> feature >> >>> >> > adds >> >>> >> > new Agent APIs for attaching a remote client to the stdin, >> >>> stdout, >> >>> >> and >> >>> >> > stderr >> >>> >> > of a running Mesos task, as well as an API for launching new >> >>> >> processes >> >>> >> > inside >> >>> >> > the same container as a running Mesos task and attaching to >> its >> >>> >> stdin, >> >>> >> > stdout, >> >>> >> > and stderr. At a high level, these APIs mimic functionality >> >>> similar >> >>> >> to >> >>> >> > docker >> >>> >> > attach and docker exec. The primary motivation for such >> >>> functionality >> >>> >> > is to >> >>> >> > enable users to debug their running Mesos tasks. >> >>> >> > >> >>> >> > * [MESOS-6758] - **Experimental** Support 'Basic' auth docker >> >>> private >> >>> >> > registry >> >>> >> > on Mesos Containerizer. Until now, the mesos containerizer >> >>> always >> >>> >> > assumed >> >>> >> > Bearer auth, but we now also support basic auth for private >> >>> >> registries. >> >>> >> > Please >> >>> >> > note that the AWS ECS uses Basic authorization but it does not >> >>> work >> >>> >> yet >> >>> >> > due to >> >>> >> > the redirect issue MESOS-5172. >> >>> >> > >> >>> >> > The CHANGELOG for the release is available at: >> >>> >> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p >> >>> >> > lain;f=CHANGELOG;hb=1.2.0-rc2 >> >>> >> > ------------------------------------------------------------ >> >>> >> > -------------------- >> >>> >> > >> >>> >> > The candidate for Mesos 1.2.0 release is available at: >> >>> >> > https://dist.apache.org/repos/dist/dev/mesos/1.2.0-rc2/ >> >>> >> mesos-1.2.0.tar.gz >> >>> >> > >> >>> >> > The tag to be voted on is 1.2.0-rc2: >> >>> >> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit >> >>> ;h=1.2.0-rc2 >> >>> >> > >> >>> >> > The MD5 checksum of the tarball can be found at: >> >>> >> > https://dist.apache.org/repos/dist/dev/mesos/1.2.0-rc2/mesos >> >>> >> > -1.2.0.tar.gz.md5 >> >>> >> > >> >>> >> > The signature of the tarball can be found at: >> >>> >> > https://dist.apache.org/repos/dist/dev/mesos/1.2.0-rc2/mesos >> >>> >> > -1.2.0.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/orgapache >> >>> mesos-1180 >> >>> >> > >> >>> >> > Please vote on releasing this package as Apache Mesos 1.2.0! >> >>> >> > >> >>> >> > The vote is open until Wed Mar 1 18:00 PST 2017 and passes if a >> >>> majority >> >>> >> of >> >>> >> > at least 3 +1 PMC votes are cast. >> >>> >> > >> >>> >> > [ ] +1 Release this package as Apache Mesos 1.2.0 >> >>> >> > [ ] -1 Do not release this package because ... >> >>> >> > >> >>> >> > Thanks, >> >>> >> > -Adam- >> >>> >> > >> >>> >> >> >>> >> >> >> >> >> > >>
