aurora-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Erb <>
Subject Re: Review Request 46603: Introduce command line option to control the offer filter duration
Date Wed, 27 Apr 2016 21:49:26 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated April 27, 2016, 11:49 p.m.)

Review request for Aurora, Maxim Khutornenko and Bill Farner.


Bill's feedback.

Bugs: AURORA-1658

Repository: aurora


Aurora is declining Mesos offers implicitly when launching a task and explicitly when compacting
multiple offers of a slave into a single one.
The filter duration instructs Mesos to return the declined resources to us only after a timeout
of X seconds, even if there is no other framework that wants them. If no filter is supplied,
the hardcoded default of 5 seconds would be used.

By making this value configurable, Aurora can be tuned for either single or multi-framework

Diffs (updated)
----- 4b810f2d808cbf0d91c753147d98d1e389106d22 
  src/jmh/java/org/apache/aurora/benchmark/ 1d725c03d16116257e1c4242ebf60f5931d4600f

  src/jmh/java/org/apache/aurora/benchmark/fakes/ d1bb8f29c9bed42c27624204b9d34ab1893468f7

  src/main/java/org/apache/aurora/scheduler/mesos/ 013c50cf70fe45fc2a74c1ea5dccccfaba14225c

  src/main/java/org/apache/aurora/scheduler/mesos/ 7ff3e3e5dc70187066b914f7feb65d99f2145303

  src/main/java/org/apache/aurora/scheduler/offers/ 452451f239a964c1b55ede3d6fbde0bd805e4b00

  src/main/java/org/apache/aurora/scheduler/offers/ PRE-CREATION 
  src/main/java/org/apache/aurora/scheduler/offers/ 90f8abf830478ad48f9a8a62c1c42423ab0f8d57

  src/main/java/org/apache/aurora/scheduler/offers/ a52fd4e8cd5c32d9560d4d72958a54bef820d81c

  src/test/java/org/apache/aurora/scheduler/offers/ 76da6d80d91221336e50d596cc2f49e890451fd1



* ./gradlew -Pq build 
* ./src/test/sh/org/apache/aurora/e2e/
I have also conducted an (unscientific) benchmark in Vagrant and started a job with 5 instances
and recorded the time from `PENDING` to `RUNNING` for the slowest ones:

* 7s startup time for a filter duration of 0 seconds
* 29s startup time for the hardcoded former default of 5 seconds


Stephan Erb

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message