On Tue, Jul 14, 2015 at 4:36 AM, Mike B <[email protected]> wrote: > I could see the master processing ACCEPT calls for offers and I could see > the resources associated with the new slave being recovered because none of > the frameworks they were offered to wanted them. What I never saw was these > new resources being offered to the framework that could have used them. > Ideally, I would have liked these new resources to have been offered to > that framework. (One note, another instance of the same framework was > launched after seeing this problem and it was offered these new resources.) > > >
I imagine this could be possible with the built-in allocator if the framework (say F) that needed the "worker" resources had a high DRF share and other frameworks had a low DRF share. If the frameworks that do not need "worker" resources do not filter them for long enough (refuse_seconds is small) time, they might repeatedly become candidates for allocation starving out F. Couple of options here. --> You can have frameworks that are not interested in "worker" resources decline offers (with "worker" resources) with a very long interval (say 1 year). --> Instead of attributes, use roles (role: worker, role: workstation etc) and have framework F register with role "worker".
