Re: [VOTE] Move Apache Mesos to Attic

+1 It has been a pleasure working with you all! On Mon, Apr 5, 2021 at 10:58 AM Vinod Kone wrote: > Hi folks, > > Based on the recent conversations > < > https://lists.apache.org/thread.html/raed89cc5ab78531c48f56aa1989e1e7eb05f89a6941e38e9bc8803ff%40%3Cuser.mesos.apache.org%3E > > > on our mai

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

+1 tested on centos 7.4, only known flakies: [ PASSED ] 466 tests. [ FAILED ] 7 tests, listed below: [ FAILED ] CgroupsIsolatorTest.ROOT_CGROUPS_CFS_EnableCfs [ FAILED ] CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_Listen [ FAILED ] DockerVolumeIsolatorTest.ROOT_CommandTaskNoRootfs

Upcoming changes to the `/role` endpoint and `GET_QUOTA` call

Hi: We are making some changes to the response of *`/role` endpoint and master `GET_QUOTA` call.* These are necessary as part of the quota limits work . Despite efforts in keeping these as backward co

Upcoming allocator change to clusters using oversubscribed resources with quota under DRF

Folks: If you are not using oversubscribed resources along with quota under DRF (all three at the same time), read no further. Just stay tuned for the upcoming shiny new allocator with decoupled quota guarantees and

Re: [VOTE] Release Apache Mesos 1.8.0 (rc3)

+1 Tested on CentOS 7.4, only known flakiness -Meng On Tue, Apr 30, 2019 at 8:14 AM Alex Rukletsov wrote: > Modulo Jorge's comment (hope he'll come back soon), > > +1 (binding). > > This rc has been deployed on a cluster internally by us at Mesosphere and > has been running without noticeable i

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

+1 sudo make check on CentOS 7.4, only known flaky tests failed On Tue, Mar 12, 2019 at 4:44 PM Gilbert Song wrote: > +1 (binding). > > -Gilbert > > On Thu, Mar 7, 2019 at 10:09 AM Greg Mann wrote: > > > +1 (binding) > > > > Ran through internal CI and observed only known flaky tests; almost al

[RESULT][VOTE] Release Apache Mesos 1.4.3 (rc2)

Hi all, The vote for Mesos 1.4.3 (rc2) has passed with the following votes. +1 (Binding) -- Vinod Kone Gastón Kleiman Gilbert Song There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.4.3 It is recommended to us

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

+1, ran through out internal CI, only flaky failures On Thu, Feb 21, 2019 at 11:41 AM Greg Mann wrote: > +1 > > Built on CentOS 7.4 and ran all tests as root. Only 3 test failures were > observed, all known flakes. > > Cheers, > Greg > > On Wed, Feb 20, 2019 at 7:12 AM Vinod Kone wrote: > >> +1

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

+1 -- ran on centos 7.4 with only known flaky tests -Meng On Wed, Feb 20, 2019 at 4:57 PM Gastón Kleiman wrote: > +1 (binding) — ran the build through Mesosphere's internal CI and only two > known flaky tests failed. > > On Tue, Feb 19, 2019 at 11:56 AM Greg Mann wrote: > >> Hi all, >> >> Plea

[VOTE] Release Apache Mesos 1.4.3 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.3. 1.4.3 includes the following: https://issues.apache.org/jira/issues/?filter=12345433 The CHANGELOG for the release is available at: htt

Re: [VOTE] Release Apache Mesos 1.7.1 (rc2)

+1 sudo make check on CentOS 7.4. All failed tests are known flaky: [ FAILED ] CgroupsIsolatorTest.ROOT_CGROUPS_CFS_EnableCfs [ FAILED ] CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_Listen [ FAILED ] NvidiaGpuTest.ROOT_INTERNET_CURL_CGROUPS_NVIDIA_GPU_NvidiaDockerImage -Meng On Fri,

[VOTE] Release Apache Mesos 1.4.3 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.3. 1.4.3 includes the following: https://issues.apache.org/jira/issues/?filter=12345433 The CHANGELOG for the release is available at: htt

Fwd: Quota 2.0 proposal

use case for setting quotas on disk with profile is not immediate. For MVP, we could stick to the design proposal and prepare to extend that when needs arise (likely in the medium term). Thoughts? Thanks, Meng On Thu, Jan 24, 2019 at 9:58 AM Meng Zhu wrote: > After the API WG sync, we wa

Re: Quota 2.0 proposal

k) Meeting ID: 574 632 536 Find your local number: https://zoom.us/u/acZYnvuO63 <https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fu%2FacZYnvuO63&sa=D&ust=1548784417513000&usg=AFQjCNGCJXDosuVT9iEhjg_KeyoBZT4XxQ> On Sun, Jan 20, 2019 at 8:07 PM Meng Zhu wrote: > Hi folks: &g

Quota 2.0 proposal

Hi folks: I am excited to propose Quota 2.0 for better resource management on Mesos, with explicit limits (decoupled from guarantee), generic quota (which can be set on resources with metadata and on more generic resources such as the number of containers) and bright shiny new APIs. You can find

Re: Proposing `Quantity`

the value in Quantity. I > left comments and suggestions in the doc. Thanks! > > On Mon, Dec 17, 2018 at 1:49 AM Meng Zhu wrote: > > > Hello: > > > > After discussing with folks, we want to propose to use `string` in the > > `Quantity` message and also leave out

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

+1 Make check pass on Ubuntu 18.04, clang 6 -Meng On Fri, Dec 21, 2018 at 2:48 PM Chun-Hung Hsiao wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.7.1. > > > 1.7.1 includes the following: > >

Re: Proposing `Quantity`

ng On Tue, Dec 11, 2018 at 12:20 PM Meng Zhu wrote: > Hi: > > We are proposing to add a primitive type `Quantity` to facilitate several > ongoing projects. The schema will be: > > message Quantity { > required string name; > optional value.scalar scalar; > } >

Proposing `Quantity`

Hi: We are proposing to add a primitive type `Quantity` to facilitate several ongoing projects. The schema will be: message Quantity { required string name; optional value.scalar scalar; } You can find more details such as motivation, current, and future use cases in this design doc

Re: New scheduler API proposal: unsuppress and clear_filter

Thanks Ben. Some thoughts below: >From a scheduler's perspective the difference between the two models is: > > (1) expressing "how much more" you need > (2) expressing an offer "matcher" > > So: > > (1) covers the middle part of the demand quantity spectrum we currently > have: unsuppressed -> inf

Re: New scheduler API proposal: unsuppress and clear_filter

ss the framework. A > REQUEST_RESOURCES call would hold an optional resource and an optional > AgentID; the case where both are empty would map onto CLEAR_FILTERS. > > > That being said, it might still be useful to in the future expose a > low-level knob for framework allow

Re: New scheduler API proposal: unsuppress and clear_filter

could take up bulk of the allocation time when they build up). On the flip side, calling CLEAR_FILTERS too often might also have performance implications (esp. if the master/allocator actors are already stressed). Thoughts? > > On Mon, Dec 3, 2018 at 6:51 PM Meng Zhu wrote: > >

Re: New scheduler API proposal: unsuppress and clear_filter

wrote: > Hi Meng, > > What would be the recommendation for framework authors on when to use > UNSUPPRESS vs CLEAR_FILTER? > > Also, should it CLEAR_FILTERS instead of CLEAR_FILTER? > > On Mon, Dec 3, 2018 at 2:26 PM Meng Zhu wrote: > >> Hi: >> >> tl;dr:

New scheduler API proposal: unsuppress and clear_filter

Hi: tl;dr: We are proposing to add two new V1 scheduler APIs: unsuppress and clear_filter in order to decouple the dual-semantics of the current revive call. As pointed out in the Mesos framework scalability guide

Re: [VOTE] Release Apache Mesos 1.5.2 (rc2)

+1 make check on Ubuntu 18.04 On Wed, Oct 31, 2018 at 4:26 PM Gilbert Song wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.5.2. > > 1.5.2 includes the following: > > > *An

Proposing Minimum Capability to Safeguard Downgrade

Hi: A common use case for downgrade is rolling back from problematic upgrades. Mesos promises compatibility between any 1.x and 1.y versions of masters/agents as long as new features are not used. However, currently there is no easy way to tell whether any “new” features are being used. And any in

Proposing change to the allocatable check in the allocator

Hi: The allocatable check in the allocator (shown below) was originally introduced to help alleviate the situation where a framework receives some resources, but no cpu/memory, thus cannot launc

Re: Adding a `FLAKY` label to flaky unit tests

+1, the advantages are appealing. Though I am afraid that this will probably reduce the incentive to fix flaky tests. -Meng On Thu, Mar 29, 2018 at 9:45 AM, Benno Evers wrote: > Hi all, > > if you're regularly running Mesos unit tests, e.g. because you've set up a > CI system, you probably not

Re: Welcome Chun-Hung Hsiao as Mesos Committer and PMC Member

Congrats Chun! Well deserved! On Mon, Mar 12, 2018 at 10:09 AM, Zhitao Li wrote: > Congrats, Chun! > > On Sun, Mar 11, 2018 at 11:47 PM, Gilbert Song > wrote: > > > Congrats, Chun! > > > > It is great to have you in the community! > > > > - Gilbert > > > > On Sun, Mar 11, 2018 at 4:40 PM, Andre

Re: Tasks may be explicitly dropped by agent in Mesos 1.5

very > to > >> > the executor. Due to the changes for MESOS-1720, one special case of > >> task > >> > re-ordering now leads to the re-ordered task being dropped (rather > than > >> > delivered out-of-order as before). Technically, this is strictly > bet

Tasks may be explicitly dropped by agent in Mesos 1.5

Hi all: TLDR: In Mesos 1.5, tasks may be explicitly dropped by the agent if all three conditions are met: (1) Several `LAUNCH_TASK` or `LAUNCH_GROUP` calls use the same executor. (2) The executor currently does not exist on the agent. (3) Due to some race conditions, these tasks are trying to lau