Re: Exponential Backoff

Would appreciate feedback/comments on this proposal. Thanks Anindya > On Feb 12, 2017, at 9:03 PM, Anindya Sinha wrote: > > Reference: https://issues.apache.org/jira/browse/MESOS-7087 > > > Currently, we have at least 3 types of backoff such

Re: Proposal for Mesos Build Improvements

Actually, this is a policy I have never been a big fan of. In my experience just forward declaring as much as possible in the headers and only including in compilations units tend to have decent improvements in complication time, particularly files like `mesos.cpp` or `slave.cpp` which indirectl

Re: Exponential Backoff

Hi Anindya, thanks for that nice systematic write up. It makes it pretty clear that there are some inconsistency how back-off is handled, and how a more systematic approach could help. I’d like to make a small remark here where I can use some more space than in the doc. >> On Feb 12, 2017, at

[GitHub] mesos issue #165: mesoscon eu - hackatron exercise - CI using travis

Github user dcaba commented on the issue: https://github.com/apache/mesos/pull/165 Hi, a bit surprised travis integration is still enabled (so all PRs have red crosses)... let me know if you want me to resolve the conflicts to integrate this (in addition to a basic travis j

Re: How to consistent handle default values for message types

On Mon, Feb 13, 2017 at 5:27 PM, Benjamin Mahler wrote: > The way I think about this is that if the field is semantically required > "semantically required": good point and this should definitely be one of the criteria. I guess we still need to clarify this for each of these messages: there's a

[GitHub] mesos issue #165: mesoscon eu - hackatron exercise - CI using travis

Github user haosdent commented on the issue: https://github.com/apache/mesos/pull/165 Hi, @dcaba Since Mesos have used Apache CI to perform testings instead of travis ci, could refer to https://issues.apache.org/jira/browse/MESOS-5655 for the details. And thx @jfarrell, he just disabl

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

-1 for https://issues.apache.org/jira/browse/MESOS-7133 > On Feb 8, 2017, at 10:39 PM, Vinod Kone wrote: > > +1 (binding) > > Tested on ASF CI. > > Revision: 5d4c9962930c3f5c08e802caff40b670424cb091 > refs/tags/1.1.1-rc1 > Configurati

task STAGING for keep long time

*centos7.3.1611* *kernel-3.10.0-514.6.1.el7.x86_64* *mesos1.2.0* *Docker version 1.13.1, build 092cba3* *taskid* alpha-common_lpt_qc_16_1_pc.1.20170216180430.251_1806_0_1_250_app *master log* mesos-master.adca-mesos-1.vm.invalid-user.log.INFO.20170215-162534.3430663:I0216 19:18:15.687566 3430683

Note about ".proto" files from Mesos 1.3.0+

Hi devs/contributors, The next time you checkout HEAD and open a .proto file, you may notice this line at the top of the file (after the Apache license, of course): syntax = "proto2"; This has been added to all our protobufs in order to allow different versions of the protobuf compiler to pr