I would like to understand how LaunchTaskMessage’s Filters work ? What’s the 
intent behind it ? I read the documentation, but got confused with "Time to 
consider unused resources refused”. Does that mean that for any resource 
allocation chunk there can be three possible states: [used, unused, refused] ? 
Also, how does allocator takes it into account. 

Another thing that I noticed was the value of refused seconds set as part of 
LaunchTaskMessage is somehow not getting honored. For example: 
https://github.com/jenkinsci/mesos-plugin/blob/master/src/main/java/org/jenkinsci/plugins/mesos/JenkinsScheduler.java#L324,
 sets the refuse seconds value to 1, but in mesos master logs, I see following:

I0310 18:28:25.381296  1153 hierarchical_allocator_process.hpp:590] Framework 
201403032301-1255541002-5050-1126-0364 filtered slave 
201403032301-1255541002-5050-1126-11 for 5secs

Basically, it’s using the default value.
--
Mohit

Reply via email to