[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450959#comment-15450959 ] Hadoop QA commented on YARN-3405: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174865#comment-15174865 ] Hadoop QA commented on YARN-3405: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742798#comment-14742798 ] Hadoop QA commented on YARN-3405: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508536#comment-14508536 ] Peng Zhang commented on YARN-3405: -- Update patch: only preempt from children when queue is

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508539#comment-14508539 ] Hadoop QA commented on YARN-3405: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508711#comment-14508711 ] Hadoop QA commented on YARN-3405: - (!) The patch artifact directory on has been removed!

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492467#comment-14492467 ] Peng Zhang commented on YARN-3405: -- Other issues for preemption during development, need

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492402#comment-14492402 ] Peng Zhang commented on YARN-3405: -- I uploaded one patch for this. This patch updated

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492482#comment-14492482 ] Hadoop QA commented on YARN-3405: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390471#comment-14390471 ] Peng Zhang commented on YARN-3405: -- bq. 2. if parent's usage reached its fair share, it

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390455#comment-14390455 ] Peng Zhang commented on YARN-3405: -- I've a primitive idea to fix this and YARN-3414 under

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14388503#comment-14388503 ] Peng Zhang commented on YARN-3405: -- I test this case in cluster: queue-2 will be preempted

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385154#comment-14385154 ] Peng Zhang commented on YARN-3405: -- Yes, changing comparator may solve this specific case,

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383615#comment-14383615 ] Peng Zhang commented on YARN-3405: -- [~zxu] I have verified that there's no problem in

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383469#comment-14383469 ] Peng Zhang commented on YARN-3405: -- And there is another related case which will cause

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383513#comment-14383513 ] zhihai xu commented on YARN-3405: - It looks like the code will still check queue-1-1(leaf

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383546#comment-14383546 ] Peng Zhang commented on YARN-3405: -- Thanks, my mistake on the code detail. And I will

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383953#comment-14383953 ] Karthik Kambatla commented on YARN-3405: [~peng.zhang] - I haven't looked at the

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385099#comment-14385099 ] Peng Zhang commented on YARN-3405: -- bq. There is a possibility for the first scenario. If

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385124#comment-14385124 ] Peng Zhang commented on YARN-3405: -- [~kasha] What the real problem I met in our cluster is

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385135#comment-14385135 ] zhihai xu commented on YARN-3405: - This issue looks like a Comparator issue, It will be