> On Jan. 20, 2016, 9:49 a.m., Qian Zhang wrote:
> > One question: Say allocation interval is 10s, at the time 5s, framework
> > sets a filter with 3s, so with this patch, we will expire the filter 10s
> > (max(10, 3)) later, i.e., at the time 15s. Then at the time of 10s (the
> > next allocation cycle), allocator will not allocate any resources to the
> > framework due to the 10s filter which is good and is the issue that we
> > intend to fix. And then in the time 12, a new slave joins, at this moment,
> > allocator will not allocate any resources to the framework too due to the
> > 10s filter, but maybe the new slave has the resources needed by the
> > framework. So my question is whether this is a reasonable behavior, do we
> > filter too much for the framework in this case?