Re: java driver/shutdown call

> *driver.method(Param1, )* > > *?* > > On Fri, Jan 12, 2018 at 10:59 AM, Anand Mazumdar <mazumdar.an...@gmail.com > > wrote: > >> Mohit, >> >> You can use the V1Mesos class that uses the v1 API internally allowing >> you to send the 'SHUTDOWN' call. We

Re: java driver/shutdown call

>> KILL. However, it seems that the SchedulerDriver class in Mesos does not >>> have a shutdownExecutor() call. >>> >>> https://github.com/apache/mesos/blob/72752fc6deb8ebcbfbd5448 >>> dc599ef3774339d31/src/java/src/org/apache/mesos/SchedulerDriver.java >>> >>> Mohit. >>> >> >> > -- Anand Mazumdar

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

t; > 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=1.4.1-rc1 >> > >> > ---- >> > >> > The candidate for Mesos 1.4.1 release is available at: >> > https://dist.apache.org/repos/dist/dev/mesos/1.4.1-rc1/mesos >> -1.4.1.tar.gz >> > >> > The tag to be voted on is 1.4.1-rc1: >> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit >> ;h=1.4.1-rc1 >> > >> > The MD5 checksum of the tarball can be found at: >> > https://dist.apache.org/repos/dist/dev/mesos/1.4.1-rc1/ >> > mesos-1.4.1.tar.gz.md5 >> > >> > The signature of the tarball can be found at: >> > https://dist.apache.org/repos/dist/dev/mesos/1.4.1-rc1/ >> > mesos-1.4.1.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 in a staging repository here: >> > https://repository.apache.org/content/repositories/orgapachemesos-1216 >> > >> > Please vote on releasing this package as Apache Mesos 1.4.1! >> > >> > The vote is open until Monday, November 13, 2017, 11:59 PM EST and >> passes >> > if a majority of at least 3 +1 PMC votes are cast. >> > >> > [ ] +1 Release this package as Apache Mesos 1.4.1 >> > [ ] -1 Do not release this package because ... >> > >> > Thanks, >> > Anand and Kapil >> > >> > > -- Anand Mazumdar

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

+1 (binding) make check passed on Ubuntu 16.04 -anand On Fri, Sep 15, 2017 at 2:12 PM, Kapil Arya wrote: > +1 (binding) > > Internal CI with Centos 6/7, Fedora 23, Debian 8, and Ubuntu 12/14/16. > > On Fri, Sep 15, 2017 at 5:08 PM, Vinod Kone wrote:

Mesos 1.4.0

Hello everyone, It's about time for Mesos 1.4.0 (somewhat late though, 1.3 rc1 was cut on 5/5) . Kapil would be the primary release manager and I would be the co-release manager. We expect to cut rc1 in the coming couple of weeks. Here's how you can help: - Set *Target Version = "1.4.0"* for

Re: Plan for upgrading protobuf==3.2.0 in Mesos

It is suggested to get your cluster upgraded > to > > 1.3.0 first, then come back and upgrade your executors and schedulers. > > > > We understand this may expose inconvenience around updating the protobuf > > dependency, so please let us know if you have any concern or further > > questions. > > > > -- > > > > Cheers, > > > > Zhitao Li and Anand Mazumdar, >

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

+1 (binding) make check passed on Ubuntu 16.04 with clang 3.6 -anand On Wed, May 3, 2017 at 10:01 AM, Vinod Kone wrote: > +1 (binding) > > *Revision*: 4154f66d6c6dde8fd2cf2bbf0bfa155f24ac55d4 > >- refs/tags/1.0.4-rc2 > > Configuration Matrix gcc clang > centos:7

Re: Plan for upgrading protobuf==3.2.0 in Mesos

dependency, so please let us know if you have any concern or further > questions. > > -- > > Cheers, > > Zhitao Li and Anand Mazumdar,

[Design doc][RFC] Agent Lifecycle Management

Hello everyone, We are working on adding support for agent lifecycle management [1] that will provide a feedback mechanism for frameworks in case of agent node failures. The existing agent lost [2] signal is not sufficient for frameworks to ascertain that a given agent node isn't coming back.

Re: High performance, low latency framework over mesos

s > connected? > > > > > > Thanks. > > > > *From:* Benjamin Mahler [mailto:bmah...@apache.org] > *Sent:* Thursday, March 16, 2017 3:12 AM > *To:* user > *Cc:* Anand Mazumdar > > *Subject:* Re: High performance, low latency framework over mesos > >

[Proposal] Media type for streaming requests/responses

Hello All, We recently added support for request streaming as part of the Debugging epic (MESOS-6460). As a follow up on that, we want your suggestions and feedback via comments on the proposal draft [1] around the media type to use for the 'Content-Type' header for streaming requests/responses.

[RESULT][VOTE] Release Apache Mesos 0.28.3 (rc1)

Hi all, The vote for Mesos 0.28.3 (rc1) has passed with the following votes. +1 (Binding) -- Alex Rukletsov Vinod Kone Benjamin Mahler +1 (Non-binding) -- Greg Mann There were no 0 or -1 votes. Please find the release at:

[VOTE] Release Apache Mesos 0.28.3 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.28.3. 0.28.3 includes the following: ** Bug * [MESOS-2043] - Framework auth fail with timeout error and never get authenticated *

Re: Mesos V1 Operator HTTP API - Java Proto Classes

We wanted to move the project away from officially supporting anything other than C++ and discuss more on if we should be responsible for publishing to the various language specific channels. However, for the time being, we had decided to include the v1 protobufs in the mesos JAR itself. (it

[HTTP API] Client Libraries

Hi, We recently committed documentation around available client libraries for the Scheduler /Executor HTTP API’s. Link to doc:

Re: Are you using New HTTP API Yet ?

Hi Chris, Currently, we don’t have any documentation listing all the library implementations. I filed MESOS-5419 to address this. Since you guys code in Scala, you might want to have a look at Mesos RxJava:

Re: Framework taking default resources even though a role is specified

FWIW, we recently fixed `mesos-execute` (command scheduler) to add support for roles. It should be available in the next release (0.29). https://issues.apache.org/jira/browse/MESOS-4744 -anand > On Apr 15, 2016, at 11:41 AM, June Taylor

Re: Error on Teardown attempt: Framework is not connected via HTTP

The `py-spark` framework looks to be driver based i.e. it uses the `MesosSchedulerDriver` underneath. You would need to use the `/teardown` endpoint that takes in the `frameworkId`as a query parameter for tearing it down. For more details, see:

Re: Native Lib vs. Rest API

One minor clarification: > * AuthN support for HTTP API: > https://issues.apache.org/jira/browse/MESOS-3923 > > ** Required in order to be able to use persistent volumes or dynamic > reservations (added in 0.25.0) You should be able to use

Re: many outstanding chronos offers

Can you try setting the flag `—offer_timeout` on the mesos master to some small value e.g. 5 minutes ? The default behavior is that a framework can keep hoarding the offered resources forever. http://mesos.apache.org/documentation/latest/configuration/

Re: How does mesos determine how much memory on a node is available for offer?

In case you don’t specify the resources via “—resources” flag when you start your agent, it picks up the default values. (Example: --resources="cpus:4;mem:1024;disk:2”) The default value for memory is here: https://github.com/apache/mesos/blob/master/src/slave/constants.cpp#L46

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

Dario, Thanks for the detailed explanation and for trying out the new API. However, this is not a bug. The output from CURL is the encoding used by Mesos for the events stream. From the user doc https://github.com/apache/mesos/blob/master/docs/scheduler_http_api.md: Master encodes each Event

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

nicer. I'm not sure about the \r part though? Is that a nice to have or does it have some other benefit? The design doc is not set in the stone since this has not been released yet. So definitely want to do the right/easy thing. On Fri, Aug 28, 2015 at 7:53 AM, Anand Mazumdar

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

multiple messages in a single chunk? You could simply create a single chunk per event. Cheers, Dario On 28.08.2015, at 19:43, Anand Mazumdar an...@mesosphere.io mailto:an...@mesosphere.io wrote: Dario, Can you shed a bit more light on what you still find puzzling about the CURL