Re: Future transfer of MesosCon 2015 videos

Thanks Dave for driving this. Thanks, Vinod > On Mar 26, 2023, at 11:57 AM, Dave Lester wrote: > > I assume the clarification is about MesosCon 2014 videos. I believe Twitter > owns the copyright to the videos which were recorded without cost to the > event by a Twitter staff member and

New PMC Chair

Hi community, Just wanted to let you all know that the board passed the resolution to elect a new PMC chair! Hearty congratulations to *Qian Zhang* for becoming the new Apache Mesos PMC chair and VP of the project. Thanks,

[VOTE] Move Apache Mesos to Attic

Hi folks, Based on the recent conversations on our mailing list, it seems to me that the majority consensus among the existing PMC is to move the project to the attic

Re: Next Steps

> > > How many man hours where spend on mesos in 2020, 2019 and 2018? > > Roughly 5-6 ppl (in 2020),10-11 (in 2019), 16-18 (in 2018)

Re: Next Steps

Hi folks, Sorry for the radio silence on my part for the last couple weeks. My Apache emails were not getting delivered to my inbox due to some filter mixup on my end. Sorry about that. I've read through the various threads and here's how I summarize the situation. We basically have 2 camps

Re: Next Steps

Good to see some interest in helping with project maintenance. Qian can you start a new email about figuring out the roadmap for the project? Thanks, Vinod > On Feb 18, 2021, at 11:18 AM, Charles-François Natali > wrote: > > Speaking as someone who contributed a few patches and would like

Next Steps

Hi folks, I would like to start a discussion around the future of the Mesos project. As you are probably aware, the number of active committers and contributors to the project have declined significantly over time. As of today, there's no active development of any features or a public release

Re: [BULK]Re: cgroup CPUSET for mesos agent

Great to hear! Thanks for the update. On Thu, Jan 14, 2021 at 5:18 PM Charles-François Natali wrote: > It's a bit old but in case it could help, we recently implemented this > at work - here's how we did it: > - the NUMA topology is exposed via agent custom resources > - the framework does the

Re: Paid help for getting csi ceph working

SERP is not available yet. We are currently working on an alternative way to get external storage into Mesos instead of using SLRP. Please watch the progress here: https://issues.apache.org/jira/browse/MESOS-10141 . MVP support will land in the upcoming release of Mesos. On Mon, Sep 7, 2020 at

Re: mesos master default drop acl

Not sure if you came across http://mesos.apache.org/documentation/latest/authorization/ but I hope it can answer your questions. On Thu, Jul 30, 2020 at 4:03 PM Marc Roos wrote: > > > Currently I am running on a testing environment with some default acl I > found[1]. I have configured

Re: getting correct metrics port from SRV records.

+Jason Kölker On Mon, Jul 27, 2020 at 1:38 PM Marc Roos wrote: > > Is there a way to identify the correct port via dns? I have created a > task with two ports[1]. But a dns srv query does not show anything > different than the port number. How can I identify the correct port? > Mesos-master

Re: fyi: mesos-dns is not registering all ip addresses

+Jason Kölker On Mon, Jul 27, 2020 at 8:03 AM Alex Evonosky wrote: > Thank you Marc for the clarification. > > > > On Mon, Jul 27, 2020 at 8:50 AM Marc Roos > wrote: > >> >> Hi Alex, >> >> My config.json is quite similar, but having "IPSources": ["netinfo", >> "mesos", "host"] >> >> You will

Re: Mesos syslog logging to error level instead of info?

I dont think I understand the problem here. Could you please elaborate more on what you are expecting and what you are seeing? Also the flags and env variables for the mesos-master process that you are using would be good to include. On Fri, Jul 24, 2020 at 5:30 AM Marc Roos wrote: > > > I have

Re: Subject: [VOTE] Release Apache Mesos 1.10.0 (rc1)

he workaround for the javah race and the fix for missing dependency on > protoc seem to be rather straightforward. > If any of these two should be considered a blocker for 1.10.0, please vote > -1. > > > > > > On Tue, May 19, 2020 at 6:55 PM Vinod Kone wrote: > >>

Re: Subject: [VOTE] Release Apache Mesos 1.10.0 (rc1)

Ran it in Apache CI. Found 2 build issues (issue 1

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

+1 (binding) Tested on ASF CI. All builds passed! *Revision*: 5f617044c969ebcfca281d043a2474c1a6b39f23 - refs/tags/1.7.3-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools [image:

Re: Number of tasks per executor and resource limits

wanted to support multiple tasks per > executor, could we leverage the mesos containeriser to easily put each task > in its own cgroup? > > > > Is it just a matter of setting 'execu > On Thu, 20 Feb 2020, 17:40 Vinod Kone, wrote: > >> Hi Charles, >> >

Re: Number of tasks per executor and resource limits

Hi Charles, We are actually working on a new feature that puts each of the tasks (of the default executor) in its own cgroup so that they can be individually limited. See https://issues.apache.org/jira/browse/MESOS-9916 . For custom executor, you would be on your own to implement the same. Also,

Re: cni iptables best practice

Hi Marc, CNI3 support is not on Mesosphere's near term roadmap given our other priorities. But if there's anyone in the community willing to work with you to develop it, as the Apache Mesos project, we'll be happy to accept the contribution (of course assuming it adheres to the project's quality

Re: Mesos master stops sending offers

The suggested info would be needed to triage this. Thanks, Vinod > On Dec 24, 2019, at 11:32 PM, Harjinder Singh Mistry > wrote: > >  > We have been encountering an intermittent issue where Chronos stops getting > resource offers from Mesos master and the scheduled jobs get stuck in

Re: New Apache Mesos Fedora Package

This is awesome. Thanks for doing this Javi. And for the help Benjamin. Thanks, Vinod > On Oct 20, 2019, at 4:46 AM, Javi Roman wrote: > > Hi all! > > I'd like to share with the Apache Mesos community the availability of > the official Apache Mesos Package for Fedora 30 [1]. > > This new

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

ll bundle boost 1.65.0, just like we did during 1.8.x. We > just adjusted our special stripped bundle to include additional headers. > > On Tue, Aug 27, 2019 at 1:39 PM Vinod Kone wrote: > >> -1 >> >> We upgraded the version of the bundled boost very late in the rele

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

-1 We upgraded the version of the bundled boost very late in the release cycle which doesn't give downstream customers (who also depend on boost) enough time to vet any compatibility/perf/other issues. I propose we revert the boost upgrade (and the corresponding code changes depending on the

Re: Draining: Failed to validate master::Call: Expecting 'type' to be present

Please read the "maintenace primitives" section in this doc http://mesos.apache.org/documentation/latest/maintenance/ and let us know if you have unanswered questions. On Wed, Aug 7, 2019 at 4:59 PM Marc Roos wrote: > > I seem to be able to add a maintenance schedule, and get also a report >

Re: Advice on how to group nodes (maybe with fault domain)

Master should be able to make offers for agents in different zones. Not sure what you are encountering? Please read http://mesos.apache.org/documentation/latest/fault-domains/ if you haven't already. On Tue, Aug 6, 2019 at 11:01 AM Marc Roos wrote: > > I have a test environment of vm's and I

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

+1 (binding). Tested in ASF CI. One build failed due to known flaky test https://issues.apache.org/jira/browse/MESOS-9594 *Revision*: 4ae06448466408d9ec96ede953208057609f0744 - refs/tags/1.8.1-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers

Re: How to Use 2 physical machine resource at the same time

Yes, If I understand your use case correctly. You can also reach out to us in slack if you want a more synchronous conversation about this. On Tue, Jul 9, 2019 at 10:19 AM Gokula Krishnan wrote: > Dear All, > > Thank you so much for your response. > > > > I

Re: How to Use 2 physical machine resource at the same time

Hi Gokula, Not sure I follow what you are asking here. What do you mean by one node is active and other passive at any point in time? Are you saying your framework (marathon?) is launching all your web-servers on a single node whereas you want them to be distributed evenly across 2 nodes? If yes,

Re: Design doc: Agent draining and deprecation of maintenance primitives

+1 Thanks, Vinod > On Jun 14, 2019, at 9:18 AM, Greg Mann wrote: > > Hi all, > Myself and a few other committers spent some time revisiting the possibility > of implementing agent draining using maintenance windows, as well as > discussing the coexistence of the existing maintenance

Re: '*.json' endpoints removed in 1.7

I propose that we revert this change and keep the ".json" endpoints in master branch and 1.8.x My reasoning is that, we have ecosystem components (e.g., mesos-dns which is yet to have a release with fix) and anecdotally a bunch of custom tooling at user sites that depend on these ".json"

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

+1 (binding) 1 failed build was due to a known flaky test. *Revision*: acefa90695a32f8e8d6361f8192a6522aeaadbb9 - refs/tags/1.8.0-rc3 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools

Re: Slack upgrade to Standard plan. Thanks Criteo

gt; From: Jie Yu [mailto:yujie@gmail.com] > Sent: 23 April 2019 19:51 > To: user > Subject: Re: Slack upgrade to Standard plan. Thanks Criteo > > Thanks Criteo friends! > > > On Tue, Apr 23, 2019 at 10:13 AM Vinod Kone > wrote: > > > Hi folks, > >

Slack upgrade to Standard plan. Thanks Criteo

Hi folks, As you probably realized today, we got our Slack upgraded from "free" plan to "standard" plan, which allows us to have unlimited message history and better analytics among other things! This would be great for our community. This upgrade has been made possible due to a general

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

+1 (binding) Ran on ASF CI. *Revision*: f5920ad1a7cbcd2423c30465dcf14948e392081b - refs/tags/1.8.0-rc2 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools [image: Success]

Re: Subject: [VOTE] Release Apache Mesos 1.8.0 (rc1)

+1 (binding) Ran it on ASF CI. *Revision*: 85462fc183a60ae18d85729bccb1fffb59aa572c - refs/tags/1.8.0-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools [image: Success]

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

+1 (binding) Ran in ASF CI. Saw some flaky tests but otherwise looks good. *Revision*: b1dbba03af23b0222d11f2b7ae936d77ef42650d - refs/tags/1.5.3-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl

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

petitions, but with a different > error. I filed ticket MESOS-9589 > <https://issues.apache.org/jira/browse/MESOS-9589> to track. > > Cheers, > Greg > > On Tue, Feb 19, 2019 at 2:41 PM Vinod Kone wrote: > > > Found a flaky test > > < > > > htt

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

+1 Ran this on ASF CI. The red builds are a flaky infra issue and a known flaky test . *Revision*: 58cc918e9acc2865bb07047d3d2dff156d1708b2 - refs/tags/1.7.2-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers

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

Found a flaky test

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

+1 (binding) Tested on ASF CI. Red builds are known flaky tests or unrelated infra issues. *Revision*: 1fee9b5365bf2424e4768dc1d5209c6c78dfece6 - refs/tags/1.4.3-rc2 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution

Re: Welcome Benno Evers as committer and PMC member!

Congratulations Benno! On Wed, Jan 30, 2019 at 3:21 PM Alex R wrote: > Folks, > > Please welcome Benno Evers as an Apache committer and PMC member of the > Apache Mesos! > > Benno has been active in the project for more than a year now and has made > significant contributions, including: > *

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

+1 Tested in ASF CI. Red builds are known flakes. *Revision*: fcfe1904e45726ca96fc6707d8b227a16664f4f8 - refs/tags/1.4.3-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools [image:

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

+1 (binding) Tested on ASF CI. Failing builds are due to missed SSL dep in the docker build file and a flaky test. *Revision*: d5678c3c5500cec72e22e775d9d048c55c128954 - refs/tags/1.7.1-rc2 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers

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

+1 (binding) Passed in ASF CI. Known flaky tests, but otherwise builds look good. *Revision*: 3088295d4156eb58d092ad9b3529b85fd33bd36e - refs/tags/1.5.2-rc3 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Failed]

Re: [Community WG] Reminder: Meeting today at 10:30 AM PST

Cloud recording for those who missed it: https://zoom.us/recording/play/8z2oHhJZIkf0xnJZ40-NtzlNdwn9ev_FuGQnlYkbdp4AFqpHbfWXdO46Us3-MyNu?continueMode=true On Mon, Jan 14, 2019 at 11:49 AM Vinod Kone wrote: > Hi folks, > > This is a reminder that we have community WG meeting today at

[DISCUSS] Updating the support and release policy

Hi folks, As discussed in the Community WG meeting today, I wanted to send out a proposal for updating the current support and release policy . Context: According to our release policy, the latest released version and last 2 released

[Community WG] Reminder: Meeting today at 10:30 AM PST

Hi folks, This is a reminder that we have community WG meeting today at 10:30 AM PST. The agenda for the meeting is here . Please feel free to add more items to the agenda. See you there, Vinod

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

y/CMakeFiles/grpc-1.10.0.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs On Wed, Jan 2, 2019 at 3:35 PM Vinod Kone wrote: > I see an issue > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/57/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbo

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

I see an issue

Re: FW: full Zookeeper authentication

Dmitrii. That approach sounds reasonable. Would you like to work on this? Are you looking for a reviewer/shepherd? On Thu, Dec 6, 2018 at 11:28 AM Kishchukov, Dmitrii (NIH/NLM/NCBI) [C] < dmitrii.kishchu...@nih.gov> wrote: > Mesos allow using only digest authentication scheme for Zookeeper.

Re: New scheduler API proposal: unsuppress and clear_filter

se filtered) offers and hence speed > up the deployment. > > -Meng > > On Mon, Dec 3, 2018 at 12:40 PM Vinod Kone wrote: > > > Hi Meng, > > > > What would be the recommendation for framework authors on when to use > > UNSUPPRESS vs CLEAR_FILTER? > &g

Re: New scheduler API proposal: unsuppress and clear_filter

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: We are proposing to add two new V1 scheduler APIs: unsuppress and >

Re: Sidecar for dynamic resource allocation in Mesos

This is great to see. Thanks for sharing! On Thu, Nov 29, 2018 at 1:59 PM Iwanowski, Maciej < maciej.iwanow...@intel.com> wrote: > Hello, > > My team at Intel has recently opensourced a Mesos-related project: > Orchestration-aware Workload Collocation Agent ( > https://github.com/intel/owca).

Re: Propose to create a Kubernetes framework for Mesos

Cameron and Michal: I would love to understand your motivations and use cases for a k8s Mesos framework in a bit more detail. Looks like you are willing to rewrite your existing app definitions into k8s API spec. At this point, why are you still interested in Mesos as a CAAS backend? Is it because

Re: Rhythm - time-based job scheduler

Great to see that you are using the v1 API as well. Would you like to be added to https://github.com/apache/mesos/blob/master/docs/api-client-libraries.md for more visibility? If yes, please do send a PR. On Fri, Nov 2, 2018 at 2:23 PM Benjamin Mahler wrote: > Thanks for sharing Michał! could

Re: Welcome Meng Zhu as PMC member and committer!

Congrats Meng! Thanks, Vinod > On Oct 31, 2018, at 4:26 PM, Gilbert Song wrote: > > Well deserved, Meng! > >> On Wed, Oct 31, 2018 at 2:36 PM Benjamin Mahler wrote: >> Please join me in welcoming Meng Zhu as a PMC member and committer! >> >> Meng has been active in the project for almost a

Re: Propose to run debug container as the same user of its parent container by default

Sounds good to me. If I understand correctly, you want to treat this is a bug and backport it to previous release branches? So, you are also asking whether backporting this bug will be considered a breaking change for any existing users? On Thu, Oct 25, 2018 at 11:46 AM James Peach wrote: > >

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

-1 Tested on ASF CI. Looks like Clang builds are failing with a build error. See example build output

Re: Request for Comments - Health Check API Proposal

One of the things we discussed when we added `CheckInfo` and `CheckStatusInfo` was to make the older `HealthCheck` and `bool healthy` field (inside `TaskStatus`) consistent with the new `Check` format. IIRC, some of the changes we wanted to do were - Deprecate `HealthCheck` and introduce a

Re: [dcos] Vote now for MesosCon 2018 proposals!

Voted! I see some really good proposals in there. Really looking forward to the final program! On Thu, Sep 20, 2018 at 11:51 AM Jörg Schad wrote: > Dear Mesos Community, > > Please take a few minutes over the next few days and review what members > of the community have submitted for MesosCon

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

I prefer 1) since you already have the fix. Thanks, Vinod > On Aug 29, 2018, at 8:44 PM, Chun-Hung Hsiao wrote: > > I found two issues when compiling with clang 3.5: > > 1. The `-Wno-inconsistent-missing-override` option added in > https://reviews.apache.org/r/67953/ > is not recognized

Re: MesosCon 2018 Location Change

+1 for Bay area Thanks, Vinod > On Aug 26, 2018, at 12:02 AM, Vaibhav Khanduja > wrote: > > +1 for bay area. > > Thx > >> On Sat, Aug 25, 2018, 3:20 PM Jörg Schad wrote: >> >> Just one more comment on the reasoning here: >> We (i.e., the PC) want MesosCon to be a user-driven conference

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

I see some flaky tests in ASF CI, that I don't see already reported. @Kapil Arya Can you take a look at https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/53 and see if the flaky tests are due to bugs in test code and not source? *Revision*:

Re: Mesos task history after restart

Mesos doesn't store task information in ZooKeeper. It is stored in Mesos master's memory and recovered from Mesos agents after a master restart / leader election. The task history can be controlled by `max_completed_frameworks`, `max_completed_tasks_per_framework` master flags. AFAICT, the

[RESULT] [VOTE] Move the project repos to gitbox

Hi, This vote has passed with 7 +1s and no 0s or -1s! +1 (binding) - Vinod Kone James Peach Zhitao Li Andrew Schwartzmeyer Jie Yu Greg Mann Gaston Kleiman I'll file an INFRA ticket to get the process in motion. Thanks, Vinod On Tue, Jul 17, 2018 at 8:27 PM Gastón Kleiman wrote

[VOTE] Move the project repos to gitbox

Hi, As discussed in another thread and in the committers sync, there seem to be heavy interest in moving our project repos ("mesos", "mesos-site") from the "git-wip" git server to the new "gitbox" server to better avail GitHub integrations. Please vote +1, 0, -1 regarding the move to gitbox. The

Re: Backport Policy

>>>> the release manager should ideally be the one who decides on this. > >>>>> > >>>>> I'm a little puzzled by this, why is the release manager involved? As > >>>>> we > >>>>> already document, backports occur when

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

+1 (binding) Ran through ASF CI. Red builds were known health check / check flaky tests. *Revision*: ae82dd5cc6f415916702897acfd3085b6387b118 - refs/tags/1.6.1-rc2 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Failed]

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

Hmm. Lot of tests failed when I ran this through ASF CI. Not sure if all of these are known flaky tests?

Re: New Mesos User Groups in the Netherlands and Belgium

Thanks for taking the lead on this Mats and Tomek! I have pushed the commit. Please keep us updated on how the meetups go! -- Vinod On Thu, Jun 21, 2018 at 8:10 AM, Tomek Janiszewski wrote: > PR: https://github.com/apache/mesos/pull/298/files > > > czw., 21 cze 2018, 14:29 użytkownik Mats

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

On Wed, May 23, 2018 at 10:00 PM, Michael Park wrote: > > > The tarball has been fixed, please vote now! > > > > 'twas BSD `tar` issues... :( > > > > Thanks, > > > > MPark > > > > On Wed, May 23, 2018 at 11:39 AM, Michael Park wrote: > > &g

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

It's empty for me too! On Wed, May 23, 2018 at 11:32 AM, Benjamin Mahler wrote: > Thanks Michael! > > Looks like the tar.gz is empty, is it just me? > > On Tue, May 22, 2018 at 10:09 PM, Michael Park wrote: > >> Hi all, >> >> Please vote on releasing the

Re: Deprecating the Python bindings

One of the production users that I know who used to depend on python bindings were https://github.com/douban. Also, apache aurora used to have an executor that depended on python bindings. I don't know what their dependencies are these days w.r.t python bindings. On Wed, May 9, 2018 at 11:51

Re: Questions about secret handling in Mesos

We do direct protobuf to JSON conversion for our API endpoints and I don't think we do any special case logic for `Secret` type in that conversion. So `value` based secrets will have their value show up in v1 (and likely v0) API endpoints. On Mon, Apr 23, 2018 at 9:25 AM, Zhitao Li

Re: This Month in Mesos - March 2018

Thanks for the update Greg! Sent from my phone > On Mar 30, 2018, at 3:08 PM, Greg Mann wrote: > > Oh hai there Apache Mesos Community! > > Back again with your monthly update on current events in the Mesosverse: > > > *Working Groups* > > Below you'll find a brief

Re: Release policy and 1.6 release schedule

I’m +1 for quarterly. Most importantly I want us to adhere to a predictable cadence. Sent from my phone > On Mar 23, 2018, at 9:21 PM, Jie Yu wrote: > > It's a burden for supporting multiple releases. > > 1.2 was released March, 2017 (1 year ago), and I know that some

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

+1 (binding) Tested on ASF CI. The red builds were known flaky tests regarding checks/health checks. *Revision*: f7e3872b0359c6095f8eeaefe408cb7dcef5bb83 - refs/tags/1.5.0-rc2 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Failed]

Re: This Month in Mesos - January 2018

Thanks Greg for the update! *Medium Posts* > Going forward, we'll be cross-posting Apache Mesos blog posts on Medium to > increase exposure, get feedback on engagement, and make it easier to share. > Check out the new Apache Mesos publication mesos> on > Medium for

Re: Questions about Pods and the Mesos Containerizer

Hi David, It's probably worth having a synchronous discussion around your proposed approach in our slack. I would like to understand if TASK_GROUP is the right primitive for your use case. On Mon, Jan 29, 2018 at 1:32 PM, David Morrison wrote: > > > On Thu, Jan 25, 2018 at

Re: Reservation status monitoring

The agents tab in Mesos WebUI should have a table for per role reservations. This is a new feature, so you might need to upgrade to the latest version to get it. On Tue, Jan 16, 2018 at 9:23 PM, 박도형 wrote: > Hi Folks, > > > > Is there a easy way to see the current overall

Re: java driver/shutdown call

t;>>>> >>>>>>> On Fri, Jan 12, 2018 at 10:59 AM, Anand Mazumdar < >>>>>>> mazumdar.an...@gmail.com> wrote: >>>>>>> >>>>>>>> Mohit, >>>>>>>> >>>>>>>>

Re: Mesos rare TASK_LOST scenario v 0.21.0

did try an upgrade to v1.2 and still found very similar issues. > > Regards, > Ajay > > On Tue, Jan 9, 2018 at 6:48 PM, Vinod Kone <vinodk...@apache.org> wrote: > >> 0.21 is really old and not supported. I highly recommend you upgrade to >> 1.3+. >> >> R

Re: Mesos rare TASK_LOST scenario v 0.21.0

0.21 is really old and not supported. I highly recommend you upgrade to 1.3+. Regarding what you are seeing, we definitely had issues in the past where the command executor didn't stay up long enough to guarantee that TASK_FINISHED was delivered to the agent; so races like above were possible.

Re: [Community WG] Cancel Jan 15th meeting for US holiday

SGTM @vinodkone > On Jan 5, 2018, at 4:43 PM, Judith Malnick wrote: > > Hi everyone, > > I'd like to propose canceling the January 15th Community working group > meeting because of Martin Luther King Jr. Day in the US. The next meeting > would then be January 29th,

Re: java driver/shutdown call

That's right. It is only available for v1 schedulers. On Fri, Jan 5, 2018 at 3:38 PM, Mohit Jaggi wrote: > Folks, > I am trying to change Apache Aurora's code to call SHUTDOWN instead of > KILL. However, it seems that the SchedulerDriver class in Mesos does not > have a

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

+1 (binding) Tested on ASF CI. Red builds are flaky tests due to the known perf core dump issue that has been fixed since. *Revision*: 17ab9ff8b35f5ec877f08698e28301bec030d010 - refs/tags/1.3.2-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools

Re: This Month in Mesos - December 2017

Thanks for the update Greg!. On Tue, Dec 12, 2017 at 3:51 PM, Greg Mann wrote: > Dear Apache Mesos Community, > > Development in Mesos has been active lately, with work taking place to > enable things like hybrid cloud and network storage support, as well as > improvements

Re: Welcome Andrew Schwartzmeyer as a new committer and PMC member!

Congrats Andy! Well deserved! On Mon, Nov 27, 2017 at 6:54 PM, Alex Evonosky wrote: > Welcome Andy! Congratulations! > > On Mon, Nov 27, 2017 at 9:48 PM, Benjamin Mahler > wrote: > >> Welcome and thanks for your contributions so far! >> >> On Mon,

Re: Is it possible to configure a mesos agent to use multiple work directories?

is not ideal. On Wed, Nov 22, 2017 at 1:57 PM, Jeff Kubina <jeff.kub...@gmail.com> wrote: > Thanks, that is what I thought. > > Why: To spread the I/O-workload of some frameworks across many disks. > > -- > Jeff Kubina > 410-988-4436 <(410)%20988-4436> > > &

Re: Is it possible to configure a mesos agent to use multiple work directories?

No. Why do you need that? On Wed, Nov 22, 2017 at 10:42 AM, Jeff Kubina wrote: > Is it possible to configure a mesos agent to use multiple work directories > (the work_dir parameter)? > >

Re: Can't really understand how do Executors can be injected...

wrote: > Vihod, > > much more clear. Thanks. > > I refined first question inline. > > On 22 November 2017 at 21:15, Vinod Kone <vinodk...@apache.org> wrote: > >> Hi Alex, >> >> See my answers below >> >> 1. Launch a

Re: Can't really understand how do Executors can be injected...

Hi Alex, See my answers below 1. Launch a task without accepting an offer (on already existing executor). > This is not currently possible. Every task needs some non-zero resources, and hence an offer, to be launched. What's your use case? > 2. Initiate an executor with no tasks (to launch

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

+1 (binding) Tested on ASF CI. The failures are due to 2 issues 1) perf core dump which was fixed in 1.5.0 and 2) flaky oversubscription test also fixed in 1.5.0. *Revision*:

Re: Quarterly Doc-a-thon Scheduling

SGTM! On Mon, Nov 20, 2017 at 10:13 AM, Judith Malnick wrote: > Hi all, > > Since the last doc-a-thon was so great, I'd love to get another on the > calendar for next quarter. > > The last one was on the 2nd Thursday of October, so It might make sense to > have the next

Re: Adding a new agent terminates existing executors?

not sufficient to keep containers >> separated by agent, what additionally is required? >> >> You might also need to specify other separate agent directories, like >> --runtime_dir, --docker_volume_checkpoint_dir, etc. Check the output of >> mesos-agent --flags. >> >>

Re: Adding a new agent terminates existing executors?

r cbcf6992-3094-4d0f-8482-4d68f68eae84 > > I1114 17:08:54.779705 6037 containerizer.cpp:2166] Destroying container > cbcf6992-3094-4d0f-8482-4d68f68eae84 in RUNNING state > > I1114 17:08:54.779737 6037 containerizer.cpp:2712] Transitioning the > state of container cbcf6992-3094-4d

Re: Adding a new agent terminates existing executors?

with --ip=127.0.0.1 > --hostname=localhost. > In /etc/hosts are > 127.1.1.1agent1 > 127.1.1.2agent2 > etc. and mesos-agent gets passed --ip=127.1.1.1 --hostname=agent1 etc. > > > On Tue, Nov 14, 2017 at 3:41 PM, Vinod Kone <vinodk...@apache.org&

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

+1 (binding) Tested on ASF CI. Couple red failure builds were due to known flaky tests, one of which is already resolved on master. *Revision*: c844db9ac7c0cef59be87438c6781bfb71adcc42 - refs/tags/1.4.1-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl

Re: Binary RPM packages for CentOS

This is great to see! Thanks for driving this Kapil. Once the official packages are vetted, we should update our website to point users to it. For new users, getting started with binary packages is infinitely better than having to build from source. Folks, please help us by testing this packages

Re: Subscribe to an active framework through HTTP API Scheduler

Someone worked on it (new operator api call) during the Mesoscon EU hackathon. They were planning to send a review once they wrap it up. On Tue, Oct 31, 2017 at 12:11 PM, Benjamin Mahler wrote: > There had been discussion to support killing tasks from the operator API, > but

  1   2   3   4   5   6   >