Craig Welch commented on YARN-3319:

The failed tests pass on my box with the patch, unrelated.  The checkstyle is 
referring to ResourceLimits, which the patch doesn't change... poking around in 
the build artifacts there are some exceptions in some of the checkstyle stuff, 
I'm not sure it's actually working correctly

> Implement a FairOrderingPolicy
> ------------------------------
>                 Key: YARN-3319
>                 URL: https://issues.apache.org/jira/browse/YARN-3319
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>            Reporter: Craig Welch
>            Assignee: Craig Welch
>         Attachments: YARN-3319.13.patch, YARN-3319.14.patch, 
> YARN-3319.17.patch, YARN-3319.35.patch, YARN-3319.39.patch, 
> YARN-3319.45.patch, YARN-3319.47.patch, YARN-3319.53.patch, 
> YARN-3319.58.patch, YARN-3319.70.patch, YARN-3319.71.patch, 
> YARN-3319.72.patch, YARN-3319.73.patch, YARN-3319.74.patch
> Implement a FairOrderingPolicy which prefers to allocate to 
> SchedulerProcesses with least current usage, very similar to the 
> FairScheduler's FairSharePolicy.  
> The Policy will offer allocations to applications in a queue in order of 
> least resources used, and preempt applications in reverse order (from most 
> resources used). This will include conditional support for sizeBasedWeight 
> style adjustment
> Optionally, based on a conditional configuration to enable sizeBasedWeight 
> (default false), an adjustment to boost larger applications (to offset the 
> natural preference for smaller applications) will adjust the resource usage 
> value based on demand, dividing it by the below value:
> Math.log1p(app memory demand) / Math.log(2);
> In cases where the above is indeterminate (two applications are equal after 
> this comparison), behavior falls back to comparison based on the application 
> id, which is generally lexically FIFO for that comparison

This message was sent by Atlassian JIRA

Reply via email to