Re: LIBPROCSES_IP

Valid point. Makes sense to drive this decision from the user and the framework. On Tue, Oct 11, 2016 at 9:32 PM, Jie Yu wrote: > > > > While I believe this particular logic of setting LIBPROCESS_ADVERTISE_IP > > to agent IP can be done in the agent (it could look at the port mapping > > as well

Re: LIBPROCSES_IP

> > While I believe this particular logic of setting LIBPROCESS_ADVERTISE_IP > to agent IP can be done in the agent (it could look at the port mapping > as well) What if there are multiple port mappings? How can the agent decide which port to be used as LIBPROCESS_ADVERTISE_PORT? On Tue, Oct 11

Re: LIBPROCSES_IP

Definitely a +1 for executor binding to 0.0.0.0, instead of doing a `gethostname` and `getaddrinfo`. But I am assuming this semantics would kick in only if LIBPROCESS_IP is not set, which should be the norm. +1 for LIBPROCESS_ADVERTISE_IP and LIBPROCESS_ADVERTISE_PORT and the onus being on the fra

Re: LIBPROCSES_IP

> libprocess should always bind to 0.0.0.0 + 1 for this On Wed, Oct 12, 2016 at 2:33 AM, Jie Yu wrote: > Hi folks, > > I was in the process of cleaning up some tech debt related to env variables > in our code base. I created an epic ticket > to

Re: Need a shepherd for MESOS-5384

Sorry for the delay Kris, I replied on the ticket. On Sat, Sep 3, 2016 at 6:09 AM, Kris Paprocki < kris.paprocki.mesos.mail...@gmail.com> wrote: > Can someone help to shepherd this ticket? > > Thanks and best regards, > > Chris >

Re: MESOS-6074 fix not available in rpms

Hi Joseph, Sorry, I missed that. Thanks. On Mon, Oct 10, 2016 at 4:59 PM, Joseph Wu wrote: > That issue was fixed in two not-yet-released versions: 1.0.2 and 1.1.0 > > See: https://issues.apache.org/jira/browse/MESOS-6074 > > On Mon, Oct 10, 2016 at 4:18 PM, Haripriya Ayyalasomayajula < > ahari

Re: mesos issue #5464: Added a completed executors history configure flag in Agent.

Hi Lijun, Apologies that this slipped through the cracks! I've gone over the patch and committed it. Nice patch, thanks! Thanks to those who reviewed it as well. Ben On Wed, Aug 31, 2016 at 8:39 PM, Lijun Tang wrote: > Hi Team, > > Can I get a committer to take a look at https://reviews.apach

LIBPROCSES_IP

Hi folks, I was in the process of cleaning up some tech debt related to env variables in our code base. I created an epic ticket to track. I searched relevant tickets fired previously, and found MESOS-3740

Re: How to shutdown mesos-agent gracefully?

Hi Ma, could you please input more background, why Maintenance feature is not best option for your request? 2016-10-11 14:47 GMT+08:00 haosdent : > gracefully means not affect running tasks? > > On Tue, Oct 11, 2016 at 2:36 PM, Klaus Ma wrote: > >> It seems there's not a way to shutdown mesos-

Re: 1.1.0 release

Folks, in preparation for Mesos 1.1.0 release we would like to ask people who have worked on features in 1.1.0 to either: * update the CHANGELOG and declare the feature implemented or experimental, make sure documentation is updated as well; * postpone to 1.2 and update the related epic; * promote

Re: [E] Re: Require GCC >= 4.9

Okay, I can add some logic to use the appropriate flag depending on the compiler version. At least that way there is some sort of stack protection for either case. Thanks, Aaron On 10/11/16, 11:14 AM, "Joris Van Remoortere" wrote: >If the only win is the introduction of that flag I would tend

Re: [E] Re: Require GCC >= 4.9

If the only win is the introduction of that flag I would tend to agree with Evers. The last time we bumped the compiler versions Cody did an analysis of all the major platforms and the ability to attain one of the required compilers easily. If we want to pursue bumping the minor versions for larg

Re: [E] Re: Require GCC >= 4.9

To be honest, I still think it's a pretty big pain to require a custom compiler for mesos. From a packagers perspective, I would have to decide if I should upload the PPA package to our repositories, backport gcc-4.9 myself, or just revert this patch in our build. It would also raise the barrier o