Re: How to kill a task gracefully?

I believe this depends on the executor being used. A kill request to mesos driver from the framework scheduler is delivered to the executor. The kill request by itself is not a guarantee that the task will be killed, until honored by the executor. So, it is possible that the executor can be

Re: Official RPMs

On 09/21/2015 03:01 PM, Vinod Kone wrote: +Jake Farrell The mesos project doesn't publish platform dependent artifacts. We currently only publish platform independent artifacts like JAR (to apache maven) and interface EGG (to PyPI). Recently we made the decision

Re: Official RPMs

Hi guys, just wanted to let you all know that we (Mesosphere) fully intend to continue supporting distributing binary packages for the current set of supported OSes (namely, Ubuntu / Debian / RedHat / CentOS as listed in [0]). Sorry that 0.24 slipped through the cracks, the person who actually

How to kill a task gracefully?

Hi mesos users, anyone knows how to kill a task running in Mesos gracefully? Thanks! Best Regards, Jerry

Re: Official RPMs

Instead of relying on a private company's closed source tooling and private infrastructure to produce packages, why can't the automation and hosting be done by Apache? The Aurora project has a packaging repo which has the tooling to build packages and uses the Apache CI infrastructure to produce

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

+1 (binding) On 21 September 2015 at 11:46, Vinod Kone wrote: > +1 (binding) > > Tested on CI for CentOS5 and CentOS6. > > On Fri, Sep 18, 2015 at 6:21 PM, Adam Bordelon wrote: > >> Hi friends, >> >> Please vote on releasing the following candidate as

Re: Reservations for multiple different agents

Rinaldo, or you may try to install or port svn libs and check whether it works. On Tue, Sep 22, 2015 at 2:25 AM, Guangya Liu wrote: > Hi Rinaldo, > > The dynamic reservation endpoint support was introduced in 0.25.0, you may > want to use the latest code to build. > > If

Re: Official RPMs

Not an easy project decision for sure, #2 adds some more work for the project and #1 can leave a bad impression of the project when a 3rd party does not keep its implementation current or maintained. Personally I tend to favor #2 as it keeps everything with the project and makes it easier for the