Thanks, Vinod. I've got those commits in the list already. We'll pull in fixes for MESOS-3055 and others for rc4. I'll give it another night for Bernd to commit the fetcher fix and for Niklas to update the oversubscription doc. Then I'll cut rc4 tomorrow and leave the new vote open until next Wednesday. See the dashboard for status on remaining issues: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12326227
Jeff, see my cherry-pick spreadsheet to see what we're planning to pull into rc4: https://docs.google.com/spreadsheets/d/14yUtwfU0mGQ7x7UcjfzZg2o1TuRMkn5SvJvetARM7JQ/edit#gid=0 If anybody has any other high priority fixes or doc updates that they want in rc4, let me know asap. On Thu, Jul 16, 2015 at 7:58 PM, Jeff Schroeder <[email protected]> wrote: > What about MESOS-3055 in 0.23? Is that going to get passed up on even if > we are going to cut another rc? > > On Thursday, July 16, 2015, Vinod Kone <[email protected]> wrote: > >> -1 so that we can cherry pick MESOS-3055. >> >> The master crash bug is MESOS-3070 >> <https://issues.apache.org/jira/browse/MESOS-3070> but the fix is >> non-trivial and the bug has been in the code base prior to 23.0. So I won't >> make 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 <[email protected]> >> wrote: >> >>> The 7 day voting period has ended with only 2 binding +1s (we needed 3) >>> and >>> no explicit -1s. >>> However, Vinod says they've found a "bug that crashes master when a >>> framework uses duplicate task ids". >>> Vinod, can you please share the new JIRA and officially vote -1 for rc3 >>> if >>> you want to call for an rc4? >>> Assuming we'll cut an rc4, I'm tracking the JIRAs/patches to pull in >>> here: >>> >>> >>> https://docs.google.com/spreadsheets/d/14yUtwfU0mGQ7x7UcjfzZg2o1TuRMkn5SvJvetARM7JQ/edit#gid=0 >>> Since the rc4 changes are minor (mostly tests) and we've heavily tested >>> rc3, the next vote will only last for 3 (business) days. >>> >>> >>> On Thu, Jul 16, 2015 at 6:38 PM, Marco Massenzio <[email protected]> >>> wrote: >>> >>> > Just to add my +1 >>> > >>> > Built & Make check on Ubuntu 14.04 >>> > With & Without SSL / libevent >>> > (no 'sudo' - can test all 4 variants this evening on rc4) >>> > >>> > — >>> > Sent from Mailbox <https://www.dropbox.com/mailbox> >>> > >>> > >>> > On Thu, Jul 16, 2015 at 3:10 PM, Timothy Chen <[email protected]> >>> wrote: >>> > >>> >> As Adam mention I also think this is not a blocker, as it only affects >>> >> the way we test the cgroup on CentOS 7.x due to a CentOS bug and >>> >> doesn't actually impact Mesos normal operations. >>> >> >>> >> My vote is +1 as well. >>> >> >>> >> Tim >>> >> >>> >> On Thu, Jul 16, 2015 at 12:10 PM, Vinod Kone <[email protected]> >>> >> wrote: >>> >> > Found a bug in HTTP API related code: MESOS-3055 >>> >> > <https://issues.apache.org/jira/browse/MESOS-3055> >>> >> > >>> >> > If we don't fix this in 0.23.0, we cannot expect the 0.24.0 >>> scheduler >>> >> > driver (that will send Calls) to properly subscribe with a 0.23.0 >>> >> master. I >>> >> > could add a work around in the driver to only send Calls if the >>> master >>> >> > version is 0.24.0, but would prefer to not have to do that. >>> >> > >>> >> > Also, on the review <https://reviews.apache.org/r/36518/> for that >>> >> bug, we >>> >> > realized that we might want to make Subscribe.force 'optional' >>> instead >>> >> 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 <[email protected] >>> > >>> >> wrote: >>> >> > >>> >> >> +1 (binding) >>> >> >> This vote has been silent for almost a week. I assume everybody's >>> busy >>> >> >> testing. My testing results: basic integration tests passed for >>> Mesos >>> >> >> 0.23.0 on CoreOS with DCOS GUI/CLI, Marathon, Chronos, Spark, HDFS, >>> >> >> Cassandra, and Kafka. >>> >> >> >>> >> >> `make check` passes on Ubuntu and CentOS, but `sudo make check` >>> fails >>> >> on >>> >> >> CentOS 7.1 due to errors in CentOS. See >>> >> >> https://issues.apache.org/jira/browse/MESOS-3050 for more details. >>> >> I'm not >>> >> >> convinced this is serious enough to do another release candidate >>> and >>> >> voting >>> >> >> round, but I'll let Tim and others chime in with their thoughts. >>> >> >> >>> >> >> If we don't get enough 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 < >>> >> >> [email protected]> >>> >> >> 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 <[email protected]> >>> >>> >> 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 containers >>> upon >>> >> >> > failover. >>> >> >> > > - Upgraded minimum required compilers to GCC 4.8+ or clang >>> 3.5+. >>> >> >> > > >>> >> >> > > as well as experimental support for: >>> >> >> > > - Fetcher Caching >>> >> >> > > - Revocable Resources >>> >> >> > > - SSL encryption >>> >> >> > > - Persistent Volumes >>> >> >> > > - Dynamic Reservations >>> >> >> > > >>> >> >> > > 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.23.0-rc3 >>> >> >> > > >>> >> >> > >>> >> >> >>> >> >>> -------------------------------------------------------------------------------- >>> >> >>> >> >> > > >>> >> >> > > The candidate for Mesos 0.23.0 release is available at: >>> >> >> > > >>> >> >> > >>> >> >> >>> >> >>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc3/mesos-0.23.0.tar.gz >>> >> >> > > >>> >> >> > > The tag to be voted on is 0.23.0-rc3: >>> >> >> > > >>> >> >> > >>> >> >> >>> >> >>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.23.0-rc3 >>> >> >> > > >>> >> >> > > The MD5 checksum of the tarball can be found at: >>> >> >> > > >>> >> >> > >>> >> >> >>> >> >>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc3/mesos-0.23.0.tar.gz.md5 >>> >> >> > > >>> >> >> > > The signature of the tarball can be found at: >>> >> >> > > >>> >> >> > >>> >> >> >>> >> >>> https://dist.apache.org/repos/dist/dev/mesos/0.23.0-rc3/mesos-0.23.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/orgapachemesos-1060 >>> >> >> > > >>> >> >> > > Please vote on releasing this package as Apache Mesos 0.23.0! >>> >> >> > > >>> >> >> > > The vote is open until Thurs July 16th, 18:00 PDT 2015 and >>> passes >>> >> if a >>> >> >> > > majority of at least 3 +1 PMC votes are cast. >>> >> >> > > >>> >> >> > > [ ] +1 Release this package as Apache Mesos 0.23.0 >>> >> >> > > [ ] -1 Do not release this package because ... >>> >> >> > > >>> >> >> > > Thanks, >>> >> >> > > -Adam- >>> >> >> > >>> >> >> >>> >> >>> > >>> > >>> >> >> > > -- > Text by Jeff, typos by iPhone >
