Thanks Bill, I'll keep an eye on that. We'll definitely try to switch over
to using this method once we understand the best practice.
Josh
On Wed, Oct 1, 2014 at 3:47 PM, Bill Farner wrote:
> Also side-note: in case you're not following AURORA-703 [1], there's a
> draft [2] of dedicated machine
Also side-note: in case you're not following AURORA-703 [1], there's a
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
Yep, makes sense. We will probably be able to rely on these coarse metrics
once we homogenize more of our task and slave configurations. We'll
definitely JIRA if that doesn't work out though!
Best,
Josh
On Wed, Oct 1, 2014 at 3:04 PM, Kevin Sweeney wrote:
> Hi Josh,
>
> Those numbers are only r
Hi Josh,
Those numbers are only rough estimates, based on ideal T-shirt-sized
instances that can be placed anywhere in the cluster. In practice we've
found this to be sufficient for high-level monitoring, combined with the
error messages the scheduler generates for pending tasks of individual
serv
Hey Kevin, thanks for the fast reply. Currently we're using scheduling
constraints for dedicated resources (which we'd like to convert to the
actual "dedicated" resource feature once it's documented). These available
slot numbers are useful at a high level but unfortunately not detailed
enough for
There is (currently undocumented) under the scheduler's /vars or /vars.json
endpoint.
empty_slots_*
See
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-
