Re: Force offer from all of the slaves

Thanks for the responses. Am unable to try "GLOG_v=1" in my production setup at this time. However, I tweaked the framework logic a bit to reject offers that don't match my requirement and "wait" till the right offer comes by. On Tue, Nov 29, 2016 at 12:02 AM, Vinod Kone

Coverity Scan: Analysis completed for Mesos

Your request for analysis of Mesos has been completed successfully. The results are available at

Re: MESOS-6233 Allow agents to re-register post a host reboot

So one thing that was brought up during offline conversations was that if the host reboot is associated with hardware change (e.g., a new memory stick): - Currently: the agent would skip the recovery (and the chance of running into incompatible agent info) and register as a new agent. -

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

+1 (binding) Tested on ASF CI. *Revision*: 52a0b0a41482da35dc736ec2fd445b6099e7a4e7 - refs/tags/0.28.3-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Success]

Re: Force offer from all of the slaves

Once you set GLOG_v, you should be able to see lines like these "Framework filtered agent for <123> seconds" On Sun, Nov 27, 2016 at 8:18 AM, haosdent wrote: > > I choose the right offer and decline the rest. > Hi, @krishnanvr Do you use up all available resources in that

How to commit code change to kafka mesos framework to fix known issues?

Hi Guys, I want to fix a problem in kafka mesos framework. https://github.com/mesos/kafka/issues/197 How could I do that? Is there any process about this? Thanks, Jared, (??) Software developer Interested in open source software, big data, Linux

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

I see LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem failing on CentOS 7 and Fedora 23, see e.g., [1]. I don't see any backports touching [2], can it be a regression or this test is know to be problematic in 0.28.x? [1] http://pastebin.com/c5PzfGF8 [2]