Re: Task Constraints

t; assigned to the slaves. All the offers being made to the master look >> correct though, which leads me to believe that the constraint solver just >> doesn't work for arbitrary attributes. >> >> We would appreciate any help you can offer. >> >> Thanks, >> Kevin >> > > -- === josh adams production engineer foursquare (gv) 415-830-4106 === foursquare.com/jobs

Re: Task Constraints

s. > > > On Mon, Jul 14, 2014 at 11:26 AM, Kevin Burg wrote: > >> I've confirmed by looking at that endpoint that new attributes are not >> being picked up and modified attributes are retaining their old values. >> This is after restarting both the slaves and

Re: Task Constraints

from AURORA-582 we are ready to roll (pun intended!) Best, Josh On Mon, Jul 14, 2014 at 11:42 AM, Josh Adams wrote: > Ah, makes sense. We'll try that. Thanks for clarifying this Kevin. > > Josh > > > On Mon, Jul 14, 2014 at 11:30 AM, Kevin Sweeney > wrote: > >&

Re: Task Constraints

lave's resources are read off the offer in this way, so I don't > see why it can't be done with attributes as well. > > Someone who understands all the places where SchedulingFilter.filter is > used might be able to fix this better than I can. > > > On Wed, Jul 1

Re: announcer implementation now available

Exciting! We'll report back as soon as we've given it a spin. Cheers, Josh On Wed, Aug 6, 2014 at 11:03 AM, Brian Wickman wrote: > An example implementation of an > announcer is now available. It can be enabled with the --announcer-enable > and --announce-e

"Could not deserialize AssignedTask" error

We're trying to upgrade to Mesos 0.19.1 to use Aurora with the new Announcer impl and we're running into this error on thermos_executor.pex when trying to run any Task. Anyone seen anything like it before? Cheers, Josh WARNING: Logging before InitGoogleLogging() is written to STDERR I0813 00:57:4

Re: "Could not deserialize AssignedTask" error

ion somewhere. Could be related to > this: https://issues.apache.org/jira/browse/THRIFT-162 > > > On Tue, Aug 12, 2014 at 6:04 PM, Josh Adams wrote: > >> We're trying to upgrade to Mesos 0.19.1 to use Aurora with the new >> Announcer impl and we're running i

Monitoring capacity headroom

Hi there, Is there a way to ask the Scheduler for a current headroom estimate (in number of potential task "slots" available) for a given TaskConfig? I understand that I could do this manually by processing /state.json on the Mesos master and joining that with info from a getJobsResult, but I'd r

Re: Monitoring capacity headroom

; > https://github.com/apache/incubator-aurora/blob/master/src/main/java/org/apache/aurora/scheduler/stats/SlotSizeCounter.java > > The constants are defined here: > > https://github.com/apache/incubator-aurora/blob/master/src/main/java/org/apache/aurora/scheduler/base/ResourceAggr

Re: Monitoring capacity headroom

individual > services. > > We've experimented with a more fine-grained simulator but have not > published any of that code. If you're convinced you need this feature > please feel free to file a ticket against us. > > Cheers, > Kevin > > On Wed, Oct 1, 2014 at 2:41 PM,

Re: Monitoring capacity headroom

gt; draft [2] of dedicated machines documentation up. > > > [1] https://issues.apache.org/jira/browse/AURORA-703 > [2] https://reviews.apache.org/r/26244/ > > -=Bill > > On Wed, Oct 1, 2014 at 3:07 PM, Josh Adams wrote: > > > Yep, makes sense. We will probably be able to