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

Note that https://issues.apache.org/jira/browse/MESOS-7714 would prevent 1.4.0 agents from being downgraded to 1.3. IMHO this is a pretty big deal when considering known issues to accept in a release. >From the versioning doc: Every (minor) release is a stable release and recommended for

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

Ran on ASF CI. Found 3 issues with tests. 1) GarbageCollectorIntegrationTest.ExitedFramework : This one seems fairly new. *@Kapil can you confirm if this is a test issue or something in the code?* 2) DiskResource Persistent Volume tests seem to

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

+1 (nonbinding) Tested by running `make check` on a debian/jessie server on AWS. On Fri, Aug 18, 2017 at 12:27 PM, Kapil Arya wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.4.0. > > 1.4.0 includes the following: >

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

Hi Benno, This does sound like a great addition to Mesos. Can you however explain how jemalloc is better than tcmalloc? I think that for such important change, we probably need some more information. Your comment in MESOS-7876 mentions that we already have tcmalloc since it is part of

[GitHub] mesos pull request #227: 1.0.1 fix

Github user pangzheng closed the pull request at: https://github.com/apache/mesos/pull/227 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #227: 1.0.1 fix

GitHub user pangzheng opened a pull request: https://github.com/apache/mesos/pull/227 1.0.1 fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/pangzheng/mesos 1.0.1-fix Alternatively you can review and apply these changes as