Sounds great! The all-revocable vs. all-guaranteed strategy seems like the
easiest to implement (just add the Capability to FrameworkInfo), but making
Myriad itself smart about high-priority vs. best-effort backfill jobs.
On Wed, Dec 2, 2015 at 6:27 AM, John Omernik wrote:
>
Hey all, just curious if there has been any discussion around supporting
oversubscription in Myriad. Based on my reading of things, Myriad would be
an awesome use case for over subscription, especially when you combine it
with the FGS. Based on what I've read on oversubscription, if Myriad was
Haven't tried it but this might be possible using label based scheduling
(MapR/YARN).
I am thinking if all CGS nodes are labeled 'Production' and FGS ones 'Non
Production'
and there are two queues one labeled 'Production' and the other 'Non
Production'.
If a job is submitted to the Non Production