[
https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858402#comment-15858402
]
Karthik Kambatla commented on YARN-6163:
----------------------------------------
Discussed this offline with [~templedf].
The following approach seems reasonable. Appreciate any inputs from others.
# When processing a starved application, preempt for enough ResourceRequests
that correspond to the current starvation.
# Track the containers (and the amount of resources) that are being starved for
this application.
# Mark the app starved again, only after all the marked containers are
preempted and a delay (twice the node heartbeat interval) has passed.
> FS Preemption is a trickle for severely starved applications
> ------------------------------------------------------------
>
> Key: YARN-6163
> URL: https://issues.apache.org/jira/browse/YARN-6163
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: fairscheduler
> Affects Versions: 2.9.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
>
> With current logic, only one RR is considered per each instance of marking an
> application starved. This marking happens only on the update call that runs
> every 500ms. Due to this, an application that is severely starved takes
> forever to reach fairshare based on preemptions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
