[jira] [Comment Edited] (YARN-4329) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in Fair Scheduler
[ https://issues.apache.org/jira/browse/YARN-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530473#comment-15530473 ] Yufei Gu edited comment on YARN-4329 at 9/28/16 6:33 PM: - Hi [~templedf], thanks for the review. I uploaded the new patch for your comments. I didn't change {code} diagnosticMessageBldr.append(" exceeds current queue or its parents" + " maximum resource allowed)."); {code} to two appends since concatenation of string constants is done at compile time. was (Author: yufeigu): Hi [~templedf], thanks for the review. I uploaded the new patch for your comments. I didn't change {code} diagnosticMessageBldr.append(" exceeds current queue or its parents" + " maximum resource allowed)."); {code} to two append clause since concatenation of string constants is done at compile time. > Allow fetching exact reason as to why a submitted app is in ACCEPTED state in > Fair Scheduler > > > Key: YARN-4329 > URL: https://issues.apache.org/jira/browse/YARN-4329 > Project: Hadoop YARN > Issue Type: Sub-task > Components: fairscheduler, resourcemanager >Reporter: Naganarasimha G R >Assignee: Yufei Gu > Attachments: YARN-4329.001.patch, YARN-4329.002.patch > > > Similar to YARN-3946, it would be useful to capture possible reason why the > Application is in accepted state in FairScheduler -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-4329) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in Fair Scheduler
[ https://issues.apache.org/jira/browse/YARN-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491714#comment-15491714 ] Yufei Gu edited comment on YARN-4329 at 9/14/16 11:14 PM: -- Close YARN-5563 to work on this one. There are some reason why an app is in ACCEPTED state but doesn't run in FairScheduler. (1) Exceed queue max apps, (2) Exceed user max apps, (3) Exceed queue maxResources, (4) Exceed maxAMShare. was (Author: yufeigu): Close YARN-5563 to work on this one. There are some reason why an app is in ACCEPTED state but doesn't run in FairScheduler. (1) queue max apps, (2) user max apps, (3) queue maxResources, (4) maxAMShare. > Allow fetching exact reason as to why a submitted app is in ACCEPTED state in > Fair Scheduler > > > Key: YARN-4329 > URL: https://issues.apache.org/jira/browse/YARN-4329 > Project: Hadoop YARN > Issue Type: Sub-task > Components: fairscheduler, resourcemanager >Reporter: Naganarasimha G R >Assignee: Yufei Gu > > Similar to YARN-3946, it would be useful to capture possible reason why the > Application is in accepted state in FairScheduler -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org