[ https://issues.apache.org/jira/browse/YARN-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766305#comment-16766305 ]
Konstantinos Karanasos commented on YARN-999: --------------------------------------------- Hi [~elgoiri], if it is an opportunistic container, it will already be killed fast, so I think you don't need a distinction between guaranteed/opportunistic (you will do preemption only in the guaranteed after the timeout). I think [~asuresh] might have worked on something related to preemption recently, but not sure. > In case of long running tasks, reduce node resource should balloon out > resource quickly by calling preemption API and suspending running task. > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: YARN-999 > URL: https://issues.apache.org/jira/browse/YARN-999 > Project: Hadoop YARN > Issue Type: Sub-task > Components: graceful, nodemanager, scheduler > Reporter: Junping Du > Priority: Major > > In current design and implementation, when we decrease resource on node to > less than resource consumption of current running tasks, tasks can still be > running until the end. But just no new task get assigned on this node > (because AvailableResource < 0) until some tasks are finished and > AvailableResource > 0 again. This is good for most cases but in case of long > running task, it could be too slow for resource setting to actually work so > preemption could be hired here. -- 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