Simple question about slave<->master latency?

2016-05-11 Thread James Vanns
Sorry for cross-posting, I was meant to send this to the dev list but sent it to the user list instead by accident! Is the latency (perhaps the weighted rolling average) between master and a slave measured? If so, is it recorded as an attribute of a slave object in the scheduler API? Cheers,

Re: Simple question about slave<->master latency?

2016-05-12 Thread James Vanns
OK. Thanks. Jim On 11 May 2016 at 19:14, haosdent <haosd...@gmail.com> wrote: > So far it isn't be measured. So you could not get it from the scheduler > API. > > On Thu, May 12, 2016 at 12:39 AM, James Vanns <jvanns@gmail.com> > wrote: > > > Sorry fo

Re: Shedding light on libmesos and libprocess threading models?

2017-10-05 Thread James Vanns
insight into the (Mesos) thread model to be sure. Cheers, Jim On 26 September 2017 at 11:18, James Vanns <jvanns@gmail.com> wrote: > Oh!? Hmm. I'll take a look - I wasn't explicitly linking against anything > uncommon other than libomp and libmesos/libprocess. I'll see what ldd s

Re: Shedding light on libmesos and libprocess threading models?

2017-09-26 Thread James Vanns
1 background thread spawned by LevelDB > - 1 backgrount thread spawned by libev > > Best regards, > Benno > > On Mon, Sep 25, 2017 at 2:24 PM, James Vanns <jvanns@gmail.com> wrote: > > > Hi guys, > > > > Can anyone shed some light on the threading models

Shedding light on libmesos and libprocess threading models?

2017-09-25 Thread James Vanns
Hi guys, Can anyone shed some light on the threading models/setup used by Mesos and/or libprocess? I've got a problem with mixing/competing thread pools! I introduced some OpenMP code and of course now I get N**2 threads started each time a different libprocess thread executes my OMP code by way

122 resources.cpp:1134] Check failed: !resource.has_role() cpus:8

2018-09-26 Thread James Vanns
Hi! It's been a looonng time since I've asked a question on this list (several years) so excuse me if this is now the wrong forum! Anyway, basically, I've got an old Mesos framework I'm resurrecting and it was developed against 0.26.x, I think. For the sheer Hell of it I just upgraded Mesos to

Re: 122 resources.cpp:1134] Check failed: !resource.has_role() cpus:8

2018-09-27 Thread James Vanns
d this line to your FrameworkInfo > to receive the newer format: > > > framework.add_capabilities()->set_type(FrameworkInfo::Capability::RESERVATION_REFINEMENT); > > > Here's the JIRA that tracked this change: > https://issues.apache.org/jira/browse/MESOS-7575 > > On Wed,