[
https://issues.apache.org/jira/browse/YARN-9277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766287#comment-16766287
]
Yufei Gu commented on YARN-9277:
--------------------------------
Hi [~uranus], some general comments, I haven't looked at the code yet.
bq. We should not preempt self
+1
bq. We should not preempt high priority job.
Correct me if I am wrong, there are no priority between Yarn jobs. Priority has
been applied to tasks inside one job, which was there before the FS preemption
overhaul. We need only priorities between mappers and reducers or other
customized priorities since AM containers are always the first priority and
have been taken care.
bq. We should not preempt container which has been running for a long time.
Makes sense if all other conditions are exactly the same.
> Add more restrictions In FairScheduler Preemption
> --------------------------------------------------
>
> Key: YARN-9277
> URL: https://issues.apache.org/jira/browse/YARN-9277
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: fairscheduler
> Reporter: Zhaohui Xin
> Assignee: Zhaohui Xin
> Priority: Major
> Attachments: YARN-9277.001.patch, YARN-9277.002.patch
>
>
>
> I think we should add more restrictions in fair scheduler preemption.
> * We should not preempt self
> * We should not preempt high priority job
> * We should not preempt container which has been running for a long time.
> * ...
--
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
