[jira] [Updated] (YARN-7701) Both RM are in standby in secure cluster

[ https://issues.apache.org/jira/browse/YARN-7701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7701: -- Affects Version/s: 2.9.0 2.8.3 3.0.0 > Both RM are in standby in

[jira] [Commented] (YARN-7619) Max AM Resource value in CS UI is different for every user

[ https://issues.apache.org/jira/browse/YARN-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312410#comment-16312410 ] Sunil G commented on YARN-7619: --- Yes [~eepayne]. I missed this after holidays. :( I ll commit this patch

[jira] [Commented] (YARN-5151) [YARN-3368] Support kill application from new YARN UI

[ https://issues.apache.org/jira/browse/YARN-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311585#comment-16311585 ] Sunil G commented on YARN-5151: --- [~GergelyNovak] Thanks for the patch. However I could not bring up UI with

[jira] [Updated] (YARN-7699) queueUsagePercentage is coming as INF for getApp REST api call

[ https://issues.apache.org/jira/browse/YARN-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7699: -- Attachment: YARN-7699.001.patch Attaching patch to fix this issue. cc/ [~rohithsharma] and [~leftnoteasy] >

[jira] [Updated] (YARN-7699) queueUsagePercentage is coming as INF for getApp REST api call

[ https://issues.apache.org/jira/browse/YARN-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7699: -- Description: REST o/p for getApp call where queueUsagePercentage is INF. Credit to [~charanh] {noformat} {

[jira] [Created] (YARN-7699) queueUsagePercentage is coming as INF for getApp REST api call

Sunil G created YARN-7699: - Summary: queueUsagePercentage is coming as INF for getApp REST api call Key: YARN-7699 URL: https://issues.apache.org/jira/browse/YARN-7699 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-6599) Support rich placement constraints in scheduler

[ https://issues.apache.org/jira/browse/YARN-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311298#comment-16311298 ] Sunil G commented on YARN-6599: --- Thanks [~leftnoteasy] for working on this. Some comments/doubts from

[jira] [Updated] (YARN-7666) Introduce scheduler specific environment variable support in ASC for better scheduling placement configurations

[ https://issues.apache.org/jira/browse/YARN-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7666: -- Attachment: YARN-7666.006.patch Fixing test case. > Introduce scheduler specific environment variable support

[jira] [Commented] (YARN-7684) The Total Memory and VCores display in the yarn UI is not correct with labeled node

[ https://issues.apache.org/jira/browse/YARN-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311006#comment-16311006 ] Sunil G commented on YARN-7684: --- Thanks [~zhaoyim] I re-opened to close this as Wont fix. and you could

[jira] [Resolved] (YARN-7684) The Total Memory and VCores display in the yarn UI is not correct with labeled node

[ https://issues.apache.org/jira/browse/YARN-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G resolved YARN-7684. --- Resolution: Won't Fix This is already covered in 2.8+ version. YARN-4484 could be backported to 2.7 as

[jira] [Reopened] (YARN-7684) The Total Memory and VCores display in the yarn UI is not correct with labeled node

[ https://issues.apache.org/jira/browse/YARN-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reopened YARN-7684: --- > The Total Memory and VCores display in the yarn UI is not correct with > labeled node >

[jira] [Updated] (YARN-7666) Introduce scheduler specific environment variable support in ASC for better scheduling placement configurations

[ https://issues.apache.org/jira/browse/YARN-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7666: -- Attachment: YARN-7666.005.patch Thanks [~leftnoteasy]. Attaching new patch post fixing test case failures. >

[jira] [Updated] (YARN-7666) Introduce scheduler specific environment variable support in ASC for better scheduling placement configurations

[ https://issues.apache.org/jira/browse/YARN-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7666: -- Attachment: YARN-7666.004.patch Fixing test case issue. > Introduce scheduler specific environment variable

[jira] [Commented] (YARN-6971) Clean up different ways to create resources

[ https://issues.apache.org/jira/browse/YARN-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309330#comment-16309330 ] Sunil G commented on YARN-6971: --- [~lovekesh.bansal] Yes, complete resource profiles and resource types is

[jira] [Commented] (YARN-7692) Resource Manager goes down when a user not included in a priority acl submits a job

[ https://issues.apache.org/jira/browse/YARN-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309318#comment-16309318 ] Sunil G commented on YARN-7692: --- Kicking jenkins again. > Resource Manager goes down when a user not

[jira] [Updated] (YARN-7666) Introduce scheduler specific environment variable support in ASC for better scheduling placement configurations

[ https://issues.apache.org/jira/browse/YARN-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7666: -- Attachment: YARN-7666.003.patch Thanks [~asuresh] and [~leftnoteasy] Yes, as mentioned we can also receive this

[jira] [Commented] (YARN-7684) The Total Memory and VCores display in the yarn UI is not correct with labeled node

[ https://issues.apache.org/jira/browse/YARN-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307727#comment-16307727 ] Sunil G commented on YARN-7684: --- I will say that clicking on NodeLabels link on nodes count wont redirect to

[jira] [Commented] (YARN-6918) Remove acls after queue delete to avoid memory leak

[ https://issues.apache.org/jira/browse/YARN-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307726#comment-16307726 ] Sunil G commented on YARN-6918: --- Got it. I guess you will be adding some DEBUG log with that info passed and

[jira] [Commented] (YARN-6918) Remove acls after queue delete to avoid memory leak

[ https://issues.apache.org/jira/browse/YARN-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306162#comment-16306162 ] Sunil G commented on YARN-6918: --- Yes. Lets move forward here. It makes sense to have {{removePermission}} to

[jira] [Commented] (YARN-7684) The Total Memory and VCores display in the yarn UI is not correct with labeled node

[ https://issues.apache.org/jira/browse/YARN-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306156#comment-16306156 ] Sunil G commented on YARN-7684: --- Yes. Using cluster resource might be solving this temporary. However we have

[jira] [Updated] (YARN-7692) Resource Manager goes down when a user not included in a priority acl submits a job

[ https://issues.apache.org/jira/browse/YARN-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7692: -- Attachment: YARN-7692.001.patch Attaching patch to avoid checking ACLs during recovery. [~rohithsharma], please

[jira] [Commented] (YARN-7692) Resource Manager goes down when a user not included in a priority acl submits a job

[ https://issues.apache.org/jira/browse/YARN-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306015#comment-16306015 ] Sunil G commented on YARN-7692: --- Thanks [~charanh]. I ll help to share a patch to avoid checking priority

[jira] [Updated] (YARN-7692) Resource Manager goes down when a user not included in a priority acl submits a job

[ https://issues.apache.org/jira/browse/YARN-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7692: -- Affects Version/s: 2.9.0 2.8.3 > Resource Manager goes down when a user not included in a

[jira] [Assigned] (YARN-7692) Resource Manager goes down when a user not included in a priority acl submits a job

[ https://issues.apache.org/jira/browse/YARN-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-7692: - Assignee: Sunil G > Resource Manager goes down when a user not included in a priority acl submits > a

[jira] [Commented] (YARN-6856) Support CLI for Node Attributes Mapping

[ https://issues.apache.org/jira/browse/YARN-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305920#comment-16305920 ] Sunil G commented on YARN-6856: --- [~naganarasimha...@apache.org], could you please rebase branch to top of

[jira] [Commented] (YARN-7494) Add muti node lookup support for better placement

[ https://issues.apache.org/jira/browse/YARN-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305095#comment-16305095 ] Sunil G commented on YARN-7494: --- YARN-7666 introduces a scheduler env map through ASC. So I moved those

[jira] [Updated] (YARN-7666) Introduce scheduler specific environment variable support in ASC for better scheduling placement configurations

[ https://issues.apache.org/jira/browse/YARN-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7666: -- Attachment: YARN-7666.002.patch Rebased patch. cc/ [~leftnoteasy] [~asuresh] [~kkaranasos] > Introduce

[jira] [Assigned] (YARN-7684) The Total Memory and VCores display in the yarn UI is not correct with labeled node

[ https://issues.apache.org/jira/browse/YARN-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-7684: - Assignee: Zhao Yi Ming > The Total Memory and VCores display in the yarn UI is not correct with >

[jira] [Commented] (YARN-7684) The Total Memory and VCores display in the yarn UI is not correct with labeled node

[ https://issues.apache.org/jira/browse/YARN-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16304418#comment-16304418 ] Sunil G commented on YARN-7684: --- I added to you as a contributor. > The Total Memory and VCores display in

[jira] [Commented] (YARN-7619) Max AM Resource value in CS UI is different for every user

[ https://issues.apache.org/jira/browse/YARN-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303895#comment-16303895 ] Sunil G commented on YARN-7619: --- +1 to latest patch. Thanks [~eepayne] I could commit later tomorrow if no

[jira] [Commented] (YARN-7242) Support specify values of different resource types in DistributedShell for easier testing

[ https://issues.apache.org/jira/browse/YARN-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303736#comment-16303736 ] Sunil G commented on YARN-7242: --- Thanks [~GergelyNovak] Could you please add few more tests # Add a case

[jira] [Commented] (YARN-6894) RM Apps API returns only active apps when query parameter queue used

[ https://issues.apache.org/jira/browse/YARN-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303636#comment-16303636 ] Sunil G commented on YARN-6894: --- Could we say like below and append to existing explanation. {noformat} All

[jira] [Commented] (YARN-5151) [YARN-3368] Support kill application from new YARN UI

[ https://issues.apache.org/jira/browse/YARN-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303631#comment-16303631 ] Sunil G commented on YARN-5151: --- Lets revive this. Its a regression compared to old UI. [~GergelyNovak],

[jira] [Commented] (YARN-7612) Add Placement Processor Framework

[ https://issues.apache.org/jira/browse/YARN-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301708#comment-16301708 ] Sunil G commented on YARN-7612: --- Yes.. Gotcha. It could be possible to have some entries in that list in that

[jira] [Comment Edited] (YARN-7612) Add Placement Processor Framework

[ https://issues.apache.org/jira/browse/YARN-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301676#comment-16301676 ] Sunil G edited comment on YARN-7612 at 12/22/17 5:14 PM: - Thanks [~asuresh] bq.That

[jira] [Commented] (YARN-7612) Add Placement Processor Framework

[ https://issues.apache.org/jira/browse/YARN-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301676#comment-16301676 ] Sunil G commented on YARN-7612: --- Thanks [~asuresh] bq.That should be OK right ? if it gets cleared up, then

[jira] [Commented] (YARN-7612) Add Placement Processor Framework

[ https://issues.apache.org/jira/browse/YARN-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301638#comment-16301638 ] Sunil G commented on YARN-7612: --- Thanks [~asuresh] bq.But Currently, and to keep things less complicated, I

[jira] [Commented] (YARN-6596) Introduce Placement Constraint Manager module

[ https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301583#comment-16301583 ] Sunil G commented on YARN-6596: --- Thanks [~kkaranasos] bq.I think we can use the same or similar API that we

[jira] [Commented] (YARN-7612) Add Placement Processor Framework

[ https://issues.apache.org/jira/browse/YARN-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300419#comment-16300419 ] Sunil G commented on YARN-7612: --- Thanks [~asuresh] and [~kkaranasos] for working on this. Some comments in

[jira] [Commented] (YARN-7669) API and interface modifications for placement constraint processor

[ https://issues.apache.org/jira/browse/YARN-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300397#comment-16300397 ] Sunil G commented on YARN-7669: --- Thanks [~asuresh]. I think we can discuss in YARN-7612 if some changes is

[jira] [Commented] (YARN-6596) Introduce Placement Constraint Manager module

[ https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300168#comment-16300168 ] Sunil G commented on YARN-6596: --- bq.Not sure if we need anything specific in the

[jira] [Commented] (YARN-6858) Attribute Manager to store and provide the attributes in RM

[ https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300058#comment-16300058 ] Sunil G commented on YARN-6858: --- [~cheersyang], This is a bit different. Node Constraints are attributes to a

[jira] [Commented] (YARN-6596) Introduce Placement Constraint Manager module

[ https://issues.apache.org/jira/browse/YARN-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300053#comment-16300053 ] Sunil G commented on YARN-6596: --- bq.Note that constraints can be defined at three levels: at the cluster

[jira] [Commented] (YARN-7676) Fix inconsistent priority ordering in Priority and SchedulerRequestKey

[ https://issues.apache.org/jira/browse/YARN-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299989#comment-16299989 ] Sunil G commented on YARN-7676: --- [~botong] Thanks for raising and thanks [~asuresh] and [~jlowe] for detailed

[jira] [Commented] (YARN-7669) [API] Introduce interfaces for placement constraint processing

[ https://issues.apache.org/jira/browse/YARN-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16298560#comment-16298560 ] Sunil G commented on YARN-7669: --- Thanks [~asuresh] and [~kkaranasos] Few doubts and comments in this patch.

[jira] [Updated] (YARN-7674) Update Timeline Reader web app address in UI2

[ https://issues.apache.org/jira/browse/YARN-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7674: -- Attachment: YARN-7674.001.patch uploading v1 version > Update Timeline Reader web app address in UI2 >

[jira] [Updated] (YARN-7620) Allow node partition filters on Queues page of new YARN UI

[ https://issues.apache.org/jira/browse/YARN-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7620: -- Summary: Allow node partition filters on Queues page of new YARN UI (was: Allow partition filters on Queues

[jira] [Commented] (YARN-7032) [ATSv2] NPE while starting hbase co-processor when HBase authorization is enabled.

[ https://issues.apache.org/jira/browse/YARN-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296918#comment-16296918 ] Sunil G commented on YARN-7032: --- jenkins came clean. +1 Committing shortly if no objections. > [ATSv2] NPE

[jira] [Commented] (YARN-7620) Allow partition filters on Queues page

[ https://issues.apache.org/jira/browse/YARN-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296872#comment-16296872 ] Sunil G commented on YARN-7620: --- Committing shortly. > Allow partition filters on Queues page >

[jira] [Commented] (YARN-7457) Delay scheduling should be an individual policy instead of part of scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294836#comment-16294836 ] Sunil G commented on YARN-7457: --- Thank you. I raised YARN-7666 to track this. > Delay scheduling should be

[jira] [Updated] (YARN-7666) Introduce scheduler specific environment variable support in ASC for better scheduling placement configurations

[ https://issues.apache.org/jira/browse/YARN-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7666: -- Attachment: YARN-7666.001.patch Attaching an initial version of patch. cc/ [~leftnoteasy] [~kkaranasos] [~Tao

[jira] [Created] (YARN-7666) Introduce scheduler specific environment variable support in ASC for better scheduling placement configurations

Sunil G created YARN-7666: - Summary: Introduce scheduler specific environment variable support in ASC for better scheduling placement configurations Key: YARN-7666 URL: https://issues.apache.org/jira/browse/YARN-7666

[jira] [Commented] (YARN-7662) [Atsv2] Remove timeline.service.address dependency for starting Timeline Reader in secure mode

[ https://issues.apache.org/jira/browse/YARN-7662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293725#comment-16293725 ] Sunil G commented on YARN-7662: --- +1 for latest patch. Looks fine to me as its similar in case of NodeManager

[jira] [Commented] (YARN-7457) Delay scheduling should be an individual policy instead of part of scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293095#comment-16293095 ] Sunil G commented on YARN-7457: --- I have uploaded patch in YARN-7494 by implementing scheduling envs. I think

[jira] [Updated] (YARN-7494) Add muti node lookup support for better placement

[ https://issues.apache.org/jira/browse/YARN-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7494: -- Attachment: YARN-7494.v1.patch v1 patch > Add muti node lookup support for better placement >

[jira] [Commented] (YARN-7619) Max AM Resource value in CS UI is different for every user

[ https://issues.apache.org/jira/browse/YARN-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292877#comment-16292877 ] Sunil G commented on YARN-7619: --- Thanks [~eepayne]. Few more minor comments # In LQ, {code} userAMLimit =

[jira] [Updated] (YARN-7633) Documentation for auto queue creation feature and related configurations

[ https://issues.apache.org/jira/browse/YARN-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7633: -- Summary: Documentation for auto queue creation feature and related configurations (was: [Documentation] Add

[jira] [Updated] (YARN-7638) Unit tests related to preemption for auto created leaf queues feature

[ https://issues.apache.org/jira/browse/YARN-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7638: -- Summary: Unit tests related to preemption for auto created leaf queues feature (was: Add unit tests for

[jira] [Commented] (YARN-7638) Add unit tests for Preemption of auto created leaf queues

[ https://issues.apache.org/jira/browse/YARN-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292117#comment-16292117 ] Sunil G commented on YARN-7638: --- Committing shortly. > Add unit tests for Preemption of auto created leaf

[jira] [Commented] (YARN-7457) Delay scheduling should be an individual policy instead of part of scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291289#comment-16291289 ] Sunil G commented on YARN-7457: --- Yes [~leftnoteasy]. In my YARN-7494 , I am already refactoring

[jira] [Updated] (YARN-7620) Allow partition filters on Queues page

[ https://issues.apache.org/jira/browse/YARN-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7620: -- Attachment: YARN-7620.003.patch Attaching same patch as #310 here are v3 patch to run jenkins. > Allow

[jira] [Commented] (YARN-7638) Add unit tests for Preemption of auto created leaf queues

[ https://issues.apache.org/jira/browse/YARN-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290937#comment-16290937 ] Sunil G commented on YARN-7638: --- [~suma.shivaprasad], Could you please check checkstyle issue (including

[jira] [Commented] (YARN-7620) Allow partition filters on Queues page

[ https://issues.apache.org/jira/browse/YARN-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290927#comment-16290927 ] Sunil G commented on YARN-7620: --- Thanks [~skmvasu] for fixing below issues in latest patch. For wider

[jira] [Commented] (YARN-7634) Queue ACL validations should validate parent queue ACLs before auto-creating leaf queues

[ https://issues.apache.org/jira/browse/YARN-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290907#comment-16290907 ] Sunil G commented on YARN-7634: --- I missed jira id while committing. Hence attaching commit sha id here

[jira] [Comment Edited] (YARN-7119) Support multiple resource types in rmadmin updateNodeResource command

[ https://issues.apache.org/jira/browse/YARN-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290703#comment-16290703 ] Sunil G edited comment on YARN-7119 at 12/14/17 10:48 AM: -- Thanks

[jira] [Updated] (YARN-7119) Support multiple resource types in rmadmin updateNodeResource command

[ https://issues.apache.org/jira/browse/YARN-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7119: -- Summary: Support multiple resource types in rmadmin updateNodeResource command (was: yarn rmadmin

[jira] [Assigned] (YARN-7624) RM gives YARNFeatureNotEnabledException even when resource profile feature is not enabled

[ https://issues.apache.org/jira/browse/YARN-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-7624: - Assignee: Sunil G > RM gives YARNFeatureNotEnabledException even when resource profile feature is > not

[jira] [Commented] (YARN-7624) RM gives YARNFeatureNotEnabledException even when resource profile feature is not enabled

[ https://issues.apache.org/jira/browse/YARN-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289642#comment-16289642 ] Sunil G commented on YARN-7624: --- In {{Client#run} {code} Map profiles; try {

[jira] [Commented] (YARN-7633) [Documentation] Add documentation for auto queue creation feature and related configurations

[ https://issues.apache.org/jira/browse/YARN-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289575#comment-16289575 ] Sunil G commented on YARN-7633: --- [~leftnoteasy], could you also please take a look. > [Documentation] Add

[jira] [Updated] (YARN-7643) Handle recovery of applications in case of auto-created leaf queue mapping

[ https://issues.apache.org/jira/browse/YARN-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7643: -- Summary: Handle recovery of applications in case of auto-created leaf queue mapping (was: Handle recovery of

[jira] [Updated] (YARN-7383) Node resource is not parsed correctly for resource names containing dot

[ https://issues.apache.org/jira/browse/YARN-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7383: -- Summary: Node resource is not parsed correctly for resource names containing dot (was: Node resource not parsed

[jira] [Commented] (YARN-7646) MR job (based on old version tarball) get failed due to incompatible resource request

[ https://issues.apache.org/jira/browse/YARN-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289475#comment-16289475 ] Sunil G commented on YARN-7646: --- Yes. I also tried with 2.8.3 {{yarn --config

[jira] [Commented] (YARN-7119) yarn rmadmin -updateNodeResource should be updated for resource types

[ https://issues.apache.org/jira/browse/YARN-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289420#comment-16289420 ] Sunil G commented on YARN-7119: --- [~maniraj...@gmail.com] Is test case failures related? > yarn rmadmin

[jira] [Comment Edited] (YARN-7619) Max AM Resource value in CS UI is different for every user

[ https://issues.apache.org/jira/browse/YARN-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289408#comment-16289408 ] Sunil G edited comment on YARN-7619 at 12/13/17 3:37 PM: - Thanks [~eepayne]

[jira] [Commented] (YARN-7619) Max AM Resource value in CS UI is different for every user

[ https://issues.apache.org/jira/browse/YARN-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289408#comment-16289408 ] Sunil G commented on YARN-7619: --- Thanks [~eepayne] bq.Although this could possibly be cleaner, I am reluctant

[jira] [Commented] (YARN-7651) branch-2 application master (MR) cannot run in 3.1 cluster

[ https://issues.apache.org/jira/browse/YARN-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289404#comment-16289404 ] Sunil G commented on YARN-7651: --- cc/ [~leftnoteasy] [~djp] [~vinodkv] [~rohithsharma] > branch-2 application

[jira] [Commented] (YARN-7507) TestNodeLabelContainerAllocation failing in trunk

[ https://issues.apache.org/jira/browse/YARN-7507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289401#comment-16289401 ] Sunil G commented on YARN-7507: --- Yes. This is failing continuously. I will try to a look today >

[jira] [Created] (YARN-7651) branch-2 application master (MR) cannot run in 3.1 cluster

Sunil G created YARN-7651: - Summary: branch-2 application master (MR) cannot run in 3.1 cluster Key: YARN-7651 URL: https://issues.apache.org/jira/browse/YARN-7651 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-7650) Queue link in old RM UI is not working correctly when node labels are enabled

Sunil G created YARN-7650: - Summary: Queue link in old RM UI is not working correctly when node labels are enabled Key: YARN-7650 URL: https://issues.apache.org/jira/browse/YARN-7650 Project: Hadoop YARN

[jira] [Commented] (YARN-7383) Node resource not parsed correctly for resource names containing dot

[ https://issues.apache.org/jira/browse/YARN-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289199#comment-16289199 ] Sunil G commented on YARN-7383: --- Jenkins came clean. Committing shortly. > Node resource not parsed

[jira] [Updated] (YARN-7536) em-table improvement for better filtering in new YARN UI

[ https://issues.apache.org/jira/browse/YARN-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7536: -- Summary: em-table improvement for better filtering in new YARN UI (was: em-table filter UX issues) > em-table

[jira] [Commented] (YARN-7536) em-table improvement for better filtering in new YARN UI

[ https://issues.apache.org/jira/browse/YARN-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289110#comment-16289110 ] Sunil G commented on YARN-7536: --- +1 on latest patch. Committing shortly. > em-table improvement for better

[jira] [Commented] (YARN-7643) Handle recovery of applications on auto-created leaf queues

[ https://issues.apache.org/jira/browse/YARN-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289100#comment-16289100 ] Sunil G commented on YARN-7643: --- i am fine with latest changes. will wait for jenkins. I ll commit tomorrow

[jira] [Commented] (YARN-7383) Node resource not parsed correctly for resource names containing dot

[ https://issues.apache.org/jira/browse/YARN-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289097#comment-16289097 ] Sunil G commented on YARN-7383: --- TestPBImplRecords is passing locally. I ll still rerun jenkins to cross

[jira] [Updated] (YARN-7641) Allow searchable filter for Application page log viewer in new YARN UI

[ https://issues.apache.org/jira/browse/YARN-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7641: -- Summary: Allow searchable filter for Application page log viewer in new YARN UI (was: Allow filter on logs

[jira] [Updated] (YARN-7119) yarn rmadmin -updateNodeResource should be updated for resource types

[ https://issues.apache.org/jira/browse/YARN-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7119: -- Target Version/s: 3.1.0, 3.0.1 (was: 3.1.0) > yarn rmadmin -updateNodeResource should be updated for resource

[jira] [Updated] (YARN-7119) yarn rmadmin -updateNodeResource should be updated for resource types

[ https://issues.apache.org/jira/browse/YARN-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7119: -- Affects Version/s: (was: YARN-3926) 3.0.0 > yarn rmadmin -updateNodeResource should

[jira] [Updated] (YARN-7119) yarn rmadmin -updateNodeResource should be updated for resource types

[ https://issues.apache.org/jira/browse/YARN-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7119: -- Target Version/s: 3.1.0 (was: YARN-3926) > yarn rmadmin -updateNodeResource should be updated for resource

[jira] [Commented] (YARN-7641) Allow filter on logs page

[ https://issues.apache.org/jira/browse/YARN-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288996#comment-16288996 ] Sunil G commented on YARN-7641: --- Committing shortly. +1 for latest patch. > Allow filter on logs page >

[jira] [Commented] (YARN-7619) Max AM Resource value in CS UI is different for every user

[ https://issues.apache.org/jira/browse/YARN-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288994#comment-16288994 ] Sunil G commented on YARN-7619: --- Thanks [~eepayne] bq. I would say it would be best to save the recomputed

[jira] [Commented] (YARN-7643) Handle recovery of applications on auto-created leaf queues

[ https://issues.apache.org/jira/browse/YARN-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288867#comment-16288867 ] Sunil G commented on YARN-7643: --- Thanks [~suma.shivaprasad] One more quick comment. {code} CSQueue queue =

[jira] [Comment Edited] (YARN-7643) Handle recovery of applications on auto-created leaf queues

[ https://issues.apache.org/jira/browse/YARN-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288758#comment-16288758 ] Sunil G edited comment on YARN-7643 at 12/13/17 6:47 AM: - Thanks

[jira] [Commented] (YARN-7643) Handle recovery of applications on auto-created leaf queues

[ https://issues.apache.org/jira/browse/YARN-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288758#comment-16288758 ] Sunil G commented on YARN-7643: --- Thanks [~suma.shivaprasad]. Some comments here. # {code} void

[jira] [Commented] (YARN-7633) [Documentation] Add documentation for auto queue creation feature and related configurations

[ https://issues.apache.org/jira/browse/YARN-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288729#comment-16288729 ] Sunil G commented on YARN-7633: --- Thanks [~suma.shivaprasad] Few comments #

[jira] [Commented] (YARN-5150) [YARN-3368] Add a sunburst chart view for queues/applications resource usage to new YARN UI

[ https://issues.apache.org/jira/browse/YARN-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287769#comment-16287769 ] Sunil G commented on YARN-5150: --- Thanks. Committing shortly > [YARN-3368] Add a sunburst chart view for

[jira] [Commented] (YARN-7620) Allow partition filters on Queues page

[ https://issues.apache.org/jira/browse/YARN-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287470#comment-16287470 ] Sunil G commented on YARN-7620: --- Patch seems fine, Tested in local cluster with and without labels.

[jira] [Commented] (YARN-7508) NPE in FiCaSchedulerApp when debug log enabled in async-scheduling mode

[ https://issues.apache.org/jira/browse/YARN-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287391#comment-16287391 ] Sunil G commented on YARN-7508: --- [~bibinchundatt] Could you please commit this patch if no issues. > NPE in

[jira] [Commented] (YARN-7119) yarn rmadmin -updateNodeResource should be updated for resource types

[ https://issues.apache.org/jira/browse/YARN-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287381#comment-16287381 ] Sunil G commented on YARN-7119: --- [~maniraj...@gmail.com] Could you please help to rebase this patch. There is

[jira] [Commented] (YARN-7624) RM gives YARNFeatureNotEnabledException even when resource profile feature is not enabled

[ https://issues.apache.org/jira/browse/YARN-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287373#comment-16287373 ] Sunil G commented on YARN-7624: --- [~cheersyang] Could you please help to share the client which u used? and on

[jira] [Comment Edited] (YARN-7640) Retrospect to enable CORS related configs by default in YARN

[ https://issues.apache.org/jira/browse/YARN-7640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287355#comment-16287355 ] Sunil G edited comment on YARN-7640 at 12/12/17 9:49 AM: - I would like to hear

<    3   4   5   6   7   8   9   10   11   12   >