[
https://issues.apache.org/jira/browse/YARN-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700789#comment-16700789
]
Manikandan R commented on YARN-7746:
------------------------------------
With this patch, TestPlacementProcessor#testSchedulerRejection is failing at
{{Assert.assertEquals(4, rej.getRequest().getAllocationRequestId());}} with
error as
java.lang.AssertionError: expected:<4> but was:<3>
Since 4th scheduling request has been added at the end, we are expecting the
same to get rejected because of queue max capacity but 3rd scheduling request
is getting rejected. With this patch in place, at times, 4th request is being
processed before 3rd while prioritisation of scheduling requests happens inside
PriorityThreadPoolExecutor. I don't think this is an issue as we are expecting
ANY last container to get rejected but not any specific container rejection.
Can you please share your views?
cc [~weiweiyagn666]
> Fix PlacementProcessor to support app priority
> ----------------------------------------------
>
> Key: YARN-7746
> URL: https://issues.apache.org/jira/browse/YARN-7746
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Manikandan R
> Priority: Major
> Attachments: YARN-7746.001.patch, YARN-7746.002.patch
>
>
> The Threadpools used in the Processor should be modified to take a priority
> blocking queue that respects application priority.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
