Karthik Kambatla commented on YARN-3405:

[~peng.zhang] - I haven't looked at the code yet; I think the issue described 
in the description exists, but don't quite see the livelock. Is this the 
confirmation you are looking for? 

The back-and-forth is a little confusing, could you update the description with 
what you think the real problem is. If there is a second problem, let us handle 
that in a different JIRA and link the two if necessary. 

> FairScheduler's preemption cannot happen between sibling in some case
> ---------------------------------------------------------------------
>                 Key: YARN-3405
>                 URL: https://issues.apache.org/jira/browse/YARN-3405
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.7.0
>            Reporter: Peng Zhang
>            Priority: Critical
> Queue hierarchy described as below:
> {noformat}
>              root
>               |         
>            queue-1        
>           /      \
> queue-1-1        queue-1-2
> {noformat}
> 1. When queue-1-1 is active and it has been assigned with all resources.
> 2. When queue-1-2 is active, and it cause some new preemption request.
> 3. But when do preemption, it now starts from root, and found queue-1 is not 
> over fairshare, so no recursion preemption to queue-1-1.
> 4. Finally queue-1-2 will be waiting for resource release form queue-1-1 
> itself.

This message was sent by Atlassian JIRA

Reply via email to