[jira] [Commented] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16502250#comment-16502250 ] Sunil Govindan commented on YARN-8399: -- Configuration reuse is causing this problem.

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16502084#comment-16502084 ] Sunil Govindan commented on YARN-8258: -- YARN-8108 issue is different. RMAuthenticationFilter and

[jira] [Assigned] (YARN-8386) App log can not be viewed from Logs tab in secure cluster

[ https://issues.apache.org/jira/browse/YARN-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan reassigned YARN-8386: Assignee: Sunil Govindan > App log can not be viewed from Logs tab in secure cluster >

[jira] [Updated] (YARN-8386) App log can not be viewed from Logs tab in secure cluster

[ https://issues.apache.org/jira/browse/YARN-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8386: - Attachment: YARN-8386.001.patch > App log can not be viewed from Logs tab in secure cluster >

[jira] [Commented] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503380#comment-16503380 ] Sunil Govindan commented on YARN-8399: -- Thanks [~rohithsharma]. Adding a test case as discussed

[jira] [Updated] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8399: - Attachment: YARN-8399.003.patch > NodeManager is giving 403 GSS exception post upgrade to 3.1 in

[jira] [Updated] (YARN-8404) RM Event dispatcher is blocked if ATS1/1.5 server is not running.

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8404: - Priority: Blocker (was: Critical) > RM Event dispatcher is blocked if ATS1/1.5 server is not

[jira] [Updated] (YARN-8404) RM Event dispatcher is blocked if ATS1/1.5 server is not running.

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8404: - Affects Version/s: 3.1.0 3.0.2 > RM Event dispatcher is blocked if

[jira] [Commented] (YARN-8401) Yarnui2 not working with out internet connection

[ https://issues.apache.org/jira/browse/YARN-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503652#comment-16503652 ] Sunil Govindan commented on YARN-8401: -- For RM UI, i can see below entry in web.xml {code:java}

[jira] [Updated] (YARN-8386) App log can not be viewed from Logs tab in secure cluster

[ https://issues.apache.org/jira/browse/YARN-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8386: - Attachment: YARN-8386.002.patch > App log can not be viewed from Logs tab in secure cluster >

[jira] [Commented] (YARN-8386) App log can not be viewed from Logs tab in secure cluster

[ https://issues.apache.org/jira/browse/YARN-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504498#comment-16504498 ] Sunil Govindan commented on YARN-8386: -- Updated v2 patch. Tested in secure and no-secure cluster

[jira] [Updated] (YARN-8197) Tracking URL in the app state does not get redirected to MR ApplicationMaster for Running applications

[ https://issues.apache.org/jira/browse/YARN-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8197: - Attachment: YARN-8197.002.patch > Tracking URL in the app state does not get redirected to MR

[jira] [Commented] (YARN-8197) Tracking URL in the app state does not get redirected to MR ApplicationMaster for Running applications

[ https://issues.apache.org/jira/browse/YARN-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492663#comment-16492663 ] Sunil Govindan commented on YARN-8197: -- Thanks [~vinodkv] and [~rkanter] I tested this in a secure

[jira] [Commented] (YARN-8197) Tracking URL in the app state does not get redirected to MR ApplicationMaster for Running applications

[ https://issues.apache.org/jira/browse/YARN-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492666#comment-16492666 ] Sunil Govindan commented on YARN-8197: -- cc [~rohithsharma] [~leftnoteasy] > Tracking URL in the app

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496698#comment-16496698 ] Sunil Govindan commented on YARN-8258: -- Attaching latest patch after correcting some checkstyle

[jira] [Updated] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8258: - Attachment: YARN-8258.003.patch > YARN webappcontext for UI2 should inherit all filters from

[jira] [Commented] (YARN-8455) Add basic acl check for all TS v2 REST APIs

[ https://issues.apache.org/jira/browse/YARN-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16527953#comment-16527953 ] Sunil Govindan commented on YARN-8455: -- Thanks [~rohithsharma] for testing and verifying the same.

[jira] [Commented] (YARN-8379) Improve balancing resources in already satisfied queues by using Capacity Scheduler preemption

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528146#comment-16528146 ] Sunil Govindan commented on YARN-8379: -- In 2.9, we have added Queue Priorities and post that the

[jira] [Updated] (YARN-8455) Add basic ACL check for all ATS v2 REST APIs

[ https://issues.apache.org/jira/browse/YARN-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8455: - Summary: Add basic ACL check for all ATS v2 REST APIs (was: Add basic acl check for all TS v2

[jira] [Commented] (YARN-8424) mapreduce job is getting submitted with negative priority as it is not handled to run with default priority(i.e: 0)

[ https://issues.apache.org/jira/browse/YARN-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523963#comment-16523963 ] Sunil Govindan commented on YARN-8424: -- In theory we can have integers. So there is ideally no

[jira] [Commented] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523958#comment-16523958 ] Sunil Govindan commented on YARN-8423: -- YARN-8463 is created. Thanks [~leftnoteasy] > GPU does not

[jira] [Created] (YARN-8463) Add more tests for GPU allocation and release scenarios

Sunil Govindan created YARN-8463: Summary: Add more tests for GPU allocation and release scenarios Key: YARN-8463 URL: https://issues.apache.org/jira/browse/YARN-8463 Project: Hadoop YARN

[jira] [Commented] (YARN-8455) Add basic acl check for all TS v2 REST APIs

[ https://issues.apache.org/jira/browse/YARN-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523982#comment-16523982 ] Sunil Govindan commented on YARN-8455: -- I think this is the first step towards reaching to a complete

[jira] [Commented] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524037#comment-16524037 ] Sunil Govindan commented on YARN-8108: -- cc [~eyang] [~vinodkv] pls help to review the change > RM

[jira] [Commented] (YARN-8459) Capacity Scheduler should properly handle container allocation on app/node when app/node being removed by scheduler

[ https://issues.apache.org/jira/browse/YARN-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524036#comment-16524036 ] Sunil Govindan commented on YARN-8459: -- Hi [~leftnoteasy] and [~cheersyang] This issue happens as

[jira] [Commented] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524053#comment-16524053 ] Sunil Govindan commented on YARN-8108: -- Thanks [~eyang] This tests failed for fair scheduler. While

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525285#comment-16525285 ] Sunil Govindan commented on YARN-8379: -- Hi [~Zian Chen] Few more comments # In

[jira] [Updated] (YARN-8401) [UI2] new ui is not accessible with out internet connection

[ https://issues.apache.org/jira/browse/YARN-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8401: - Summary: [UI2] new ui is not accessible with out internet connection (was: Yarnui2 not working

[jira] [Commented] (YARN-8401) Yarnui2 not working with out internet connection

[ https://issues.apache.org/jira/browse/YARN-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525320#comment-16525320 ] Sunil Govindan commented on YARN-8401: -- [~bibinchundatt] This looks good. I will commit this

[jira] [Updated] (YARN-8453) Additional Unit tests to verify queue limit and max-limit with multiple resource types

[ https://issues.apache.org/jira/browse/YARN-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8453: - Description: Post support of additional resource types other then CPU and Memory, it could be

[jira] [Updated] (YARN-8453) Additional Unit tests to verify queue limit and max-limit with multiple resource types

[ https://issues.apache.org/jira/browse/YARN-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8453: - Summary: Additional Unit tests to verify queue limit and max-limit with multiple resource types

[jira] [Commented] (YARN-8453) Additional Unit tests to verify queue limit and max-limit with multiple resource types

[ https://issues.apache.org/jira/browse/YARN-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525522#comment-16525522 ] Sunil Govindan commented on YARN-8453: -- [~leftnoteasy] , cud u pls help to check this. > Additional

[jira] [Updated] (YARN-8453) Additional Unit tests to verify queue limit and max-limit with multiple resource types

[ https://issues.apache.org/jira/browse/YARN-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8453: - Attachment: YARN-8453.001.patch > Additional Unit tests to verify queue limit and max-limit with

[jira] [Commented] (YARN-8469) [UI2] URL needs to be trimmed to handle index.html redirection while accessing via knox

[ https://issues.apache.org/jira/browse/YARN-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525587#comment-16525587 ] Sunil Govindan commented on YARN-8469: -- [~rohithsharma] cud u pls review this. > [UI2] URL needs to

[jira] [Updated] (YARN-8469) [UI2] URL needs to be trimmed to handle index.html redirection while accessing via knox

[ https://issues.apache.org/jira/browse/YARN-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8469: - Attachment: YARN-8469.001.patch > [UI2] URL needs to be trimmed to handle index.html redirection

[jira] [Created] (YARN-8469) [UI2] URL needs to be trimmed to handle index.html redirection while accessing via knox

Sunil Govindan created YARN-8469: Summary: [UI2] URL needs to be trimmed to handle index.html redirection while accessing via knox Key: YARN-8469 URL: https://issues.apache.org/jira/browse/YARN-8469

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525713#comment-16525713 ] Sunil Govindan commented on YARN-8379: -- Thanks [~Zian Chen]. Latest patch looks good to me. +1 > Add

[jira] [Created] (YARN-8457) Compilation is broken with -Pyarn-ui

Sunil Govindan created YARN-8457: Summary: Compilation is broken with -Pyarn-ui Key: YARN-8457 URL: https://issues.apache.org/jira/browse/YARN-8457 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-8457) Compilation is broken with -Pyarn-ui

[ https://issues.apache.org/jira/browse/YARN-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8457: - Attachment: YARN-8457.patch > Compilation is broken with -Pyarn-ui >

[jira] [Commented] (YARN-8457) Compilation is broken with -Pyarn-ui

[ https://issues.apache.org/jira/browse/YARN-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522484#comment-16522484 ] Sunil Govindan commented on YARN-8457: -- cc [~rohithsharma] pls help to review > Compilation is

[jira] [Created] (YARN-8453) Allocation to a queue is dishonored if one resource is at the limit

Sunil Govindan created YARN-8453: Summary: Allocation to a queue is dishonored if one resource is at the limit Key: YARN-8453 URL: https://issues.apache.org/jira/browse/YARN-8453 Project: Hadoop YARN

[jira] [Commented] (YARN-8453) Allocation to a queue is dishonored if one resource is at the limit

[ https://issues.apache.org/jira/browse/YARN-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520753#comment-16520753 ] Sunil Govindan commented on YARN-8453: -- cc / [~leftnoteasy] > Allocation to a queue is dishonored if

[jira] [Commented] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523071#comment-16523071 ] Sunil Govindan commented on YARN-8108: -- Post YARN-7605, we need a way to safely protect servlet

[jira] [Updated] (YARN-8460) 'yarn.cluster.max-application-priority' need to be exposed via CLI/REST

[ https://issues.apache.org/jira/browse/YARN-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8460: - Summary: 'yarn.cluster.max-application-priority' need to be exposed via CLI/REST (was: please

[jira] [Commented] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523053#comment-16523053 ] Sunil Govindan commented on YARN-8423: -- Thanks [~leftnoteasy] Quickly fixed this issue. Somehow test

[jira] [Updated] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8423: - Attachment: YARN-8423.003.patch > GPU does not get released even though the application gets

[jira] [Updated] (YARN-8108) RM metrics rest API throws GSSException in kerberized environment

[ https://issues.apache.org/jira/browse/YARN-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8108: - Attachment: YARN-8108.002.patch > RM metrics rest API throws GSSException in kerberized

[jira] [Commented] (YARN-8446) Support of managing multi-dimensional resources

[ https://issues.apache.org/jira/browse/YARN-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520585#comment-16520585 ] Sunil Govindan commented on YARN-8446: -- This looks very interesting. Thanks [~cheersyang] for filing

[jira] [Created] (YARN-8450) Blocking resources such as GPU/FPGA etc tend to release actual device even after RM identifies it as COMPLETED

Sunil Govindan created YARN-8450: Summary: Blocking resources such as GPU/FPGA etc tend to release actual device even after RM identifies it as COMPLETED Key: YARN-8450 URL:

[jira] [Updated] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8423: - Attachment: YARN-8423.002.patch > GPU does not get released even though the application gets

[jira] [Commented] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520682#comment-16520682 ] Sunil Govindan commented on YARN-8423: -- Thanks [~vinodkv] Attaching new patch after addressing all

[jira] [Updated] (YARN-8450) Blocking resources such as GPU/FPGA etc tend to release actual device slowly even after RM identifies it as COMPLETED

[ https://issues.apache.org/jira/browse/YARN-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8450: - Summary: Blocking resources such as GPU/FPGA etc tend to release actual device slowly even after

[jira] [Updated] (YARN-8464) Application does not get to Running state even with available resources on node managers when async scheduling is enabled

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8464: - Attachment: YARN-8464.001.patch > Application does not get to Running state even with available

[jira] [Commented] (YARN-8464) Application does not get to Running state even with available resources on node managers when async scheduling is enabled

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524308#comment-16524308 ] Sunil Govindan commented on YARN-8464: -- Thanks [~leftnoteasy] for helping in debugging same.

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524396#comment-16524396 ] Sunil Govindan commented on YARN-8258: -- Test case failure is not related to this patch. YARN-7548 is

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524407#comment-16524407 ] Sunil Govindan commented on YARN-8258: -- cc [~eyang] and [~vinodkv] > YARN webappcontext for UI2

[jira] [Commented] (YARN-8466) Add Chaos Monkey unit test framework for feature validation in scale

[ https://issues.apache.org/jira/browse/YARN-8466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1652#comment-1652 ] Sunil Govindan commented on YARN-8466: -- Thanks [~leftnoteasy] for proposing this and [~cheersyang]

[jira] [Created] (YARN-8464) Application does not get to Running state even with available resources on node managers when async scheduling is enabled

Sunil Govindan created YARN-8464: Summary: Application does not get to Running state even with available resources on node managers when async scheduling is enabled Key: YARN-8464 URL:

[jira] [Commented] (YARN-8460) 'yarn.cluster.max-application-priority' need to be exposed via CLI/REST

[ https://issues.apache.org/jira/browse/YARN-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524318#comment-16524318 ] Sunil Govindan commented on YARN-8460: -- Thanks [~cheersyang]  Yes, this is definitely a doable way

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524256#comment-16524256 ] Sunil Govindan commented on YARN-8258: -- Post YARN-8108, this patch seems fine to go in. We have

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524263#comment-16524263 ] Sunil Govindan commented on YARN-8379: -- Thanks [~eepayne]. I will be having bandwidth to check this.

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524399#comment-16524399 ] Sunil Govindan commented on YARN-8258: -- Also attaching screen shot of UI2 in safari. This loads fine.

[jira] [Updated] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8258: - Attachment: Screen Shot 2018-06-26 at 5.54.35 PM.png > YARN webappcontext for UI2 should inherit

[jira] [Commented] (YARN-8459) Capacity Scheduler should properly handle container allocation on app/node when app/node being removed by scheduler

[ https://issues.apache.org/jira/browse/YARN-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524276#comment-16524276 ] Sunil Govindan commented on YARN-8459: -- Thanks [~leftnoteasy] This makes sense to me. Some comments

[jira] [Updated] (YARN-8464) Async scheduling thread could be interrupted when there are no NodeManagers in cluster

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8464: - Summary: Async scheduling thread could be interrupted when there are no NodeManagers in cluster

[jira] [Commented] (YARN-8464) Async scheduling thread could be interrupted when there are no NodeManagers in cluster

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524315#comment-16524315 ] Sunil Govindan commented on YARN-8464: -- yes [~leftnoteasy] Make sense. Updated patch addressing the

[jira] [Updated] (YARN-8464) Async scheduling thread could be interrupted when there are no NodeManagers in cluster

[ https://issues.apache.org/jira/browse/YARN-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8464: - Attachment: YARN-8464.002.patch > Async scheduling thread could be interrupted when there are no

[jira] [Updated] (YARN-8415) TimelineWebServices.getEntity should throw ForbiddenException instead of 404 when ACL checks fail

[ https://issues.apache.org/jira/browse/YARN-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8415: - Summary: TimelineWebServices.getEntity should throw ForbiddenException instead of 404 when ACL

[jira] [Commented] (YARN-8459) Improve logs of Capacity Scheduler to better debug invalid states

[ https://issues.apache.org/jira/browse/YARN-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530411#comment-16530411 ] Sunil Govindan commented on YARN-8459: -- Thanks [~leftnoteasy]. Latest change seems fine. It covers

[jira] [Commented] (YARN-8473) Containers being launched as app tears down can leave containers in NEW state

[ https://issues.apache.org/jira/browse/YARN-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531946#comment-16531946 ] Sunil Govindan commented on YARN-8473: -- Thanks [~jlowe] for the details. I think the patch looks good

[jira] [Commented] (YARN-7863) Modify placement constraints to support node attributes

[ https://issues.apache.org/jira/browse/YARN-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567127#comment-16567127 ] Sunil Govindan commented on YARN-7863: -- Attached rebased patch.   [~cheersyang], these constraints

[jira] [Commented] (YARN-7159) Normalize unit of resource objects in RM and avoid to do unit conversion in critical path

[ https://issues.apache.org/jira/browse/YARN-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567052#comment-16567052 ] Sunil Govindan commented on YARN-7159: -- Sorry. patch command works on this. Hence no worries. Thanks.

[jira] [Updated] (YARN-7159) Normalize unit of resource objects in RM to avoid unit conversion in critical path

[ https://issues.apache.org/jira/browse/YARN-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-7159: - Summary: Normalize unit of resource objects in RM to avoid unit conversion in critical path

[jira] [Updated] (YARN-7863) Modify placement constraints to support node attributes

[ https://issues.apache.org/jira/browse/YARN-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-7863: - Attachment: YARN-7863-YARN-3409.004.patch > Modify placement constraints to support node

[jira] [Commented] (YARN-7159) Normalize unit of resource objects in RM and avoid to do unit conversion in critical path

[ https://issues.apache.org/jira/browse/YARN-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567034#comment-16567034 ] Sunil Govindan commented on YARN-7159: -- [~maniraj...@gmail.com] I think patch needs a rebase. Not

[jira] [Updated] (YARN-7957) Yarn service delete option disappears after stopping application

[ https://issues.apache.org/jira/browse/YARN-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-7957: - Attachment: (was: YARN-7957.01.patch) > Yarn service delete option disappears after stopping

[jira] [Commented] (YARN-8620) [UI2] YARN Services UI new submission failures are not debuggable

[ https://issues.apache.org/jira/browse/YARN-8620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567877#comment-16567877 ] Sunil Govindan commented on YARN-8620: -- Thanks [~akhilpb]. This is really helpful change. Few minor

[jira] [Commented] (YARN-8608) [UI2] No information available per application appAttempt about 'Total Outstanding Resource Requests'

[ https://issues.apache.org/jira/browse/YARN-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567953#comment-16567953 ] Sunil Govindan commented on YARN-8608: -- Thanks [~akhilpb]. Looks good for me too > [UI2] No

[jira] [Commented] (YARN-8615) [UI2] Resource Usage tab shows only memory related info. No info available for vcores/gpu.

[ https://issues.apache.org/jira/browse/YARN-8615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568011#comment-16568011 ] Sunil Govindan commented on YARN-8615: -- Thanks [~akhilpb]. Looks good to me. > [UI2] Resource Usage

[jira] [Commented] (YARN-8620) [UI2] YARN Services UI new submission failures are not debuggable

[ https://issues.apache.org/jira/browse/YARN-8620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568014#comment-16568014 ] Sunil Govindan commented on YARN-8620: -- Looks good to me. Thanks. > [UI2] YARN Services UI new

[jira] [Commented] (YARN-8615) [UI2] Resource Usage tab shows only memory related info. No info available for vcores/gpu.

[ https://issues.apache.org/jira/browse/YARN-8615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567867#comment-16567867 ] Sunil Govindan commented on YARN-8615: -- Thanks [~akhilpb]. Patch looks fine.  Few minor comments #

[jira] [Commented] (YARN-8603) [UI2] Latest run application should be listed first in the RM UI

[ https://issues.apache.org/jira/browse/YARN-8603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567952#comment-16567952 ] Sunil Govindan commented on YARN-8603: -- Thanks [~akhilpb]. Looks good for me too > [UI2] Latest run

[jira] [Commented] (YARN-8620) [UI2] YARN Services UI new submission failures are not debuggable

[ https://issues.apache.org/jira/browse/YARN-8620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568229#comment-16568229 ] Sunil Govindan commented on YARN-8620: -- +1 > [UI2] YARN Services UI new submission failures are not

[jira] [Commented] (YARN-8558) NM recovery level db not cleaned up properly on container finish

[ https://issues.apache.org/jira/browse/YARN-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561754#comment-16561754 ] Sunil Govindan commented on YARN-8558: -- Apart from CONTAINER_RESTART_TIMES_SUFFIX, I am not seeing

[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=16561370#comment-16561370 ] Sunil Govindan commented on YARN-7494: -- [~leftnoteasy] [~cheersyang] pls help to review. > Add muti

[jira] [Updated] (YARN-7863) Modify placement constraints to support node attributes

[ https://issues.apache.org/jira/browse/YARN-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-7863: - Attachment: YARN-7863-YARN-3409.003.patch > Modify placement constraints to support node

[jira] [Comment Edited] (YARN-7863) Modify placement constraints to support node attributes

[ https://issues.apache.org/jira/browse/YARN-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558728#comment-16558728 ] Sunil Govindan edited comment on YARN-7863 at 7/26/18 6:35 PM: --- Thanks

[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=16559429#comment-16559429 ] Sunil Govindan commented on YARN-7494: -- Fixed test case, > Add muti node lookup support for better

[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 Govindan updated YARN-7494: - Attachment: YARN-7494.11.patch > Add muti node lookup support for better placement >

[jira] [Comment Edited] (YARN-8558) NM recovery level db not cleaned up properly on container finish

[ https://issues.apache.org/jira/browse/YARN-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559539#comment-16559539 ] Sunil Govindan edited comment on YARN-8558 at 7/27/18 10:29 AM: +1 on this

[jira] [Commented] (YARN-8558) NM recovery level db not cleaned up properly on container finish

[ https://issues.apache.org/jira/browse/YARN-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559539#comment-16559539 ] Sunil Govindan commented on YARN-8558: -- +1 on this latest patch. Thanks [~bibinchundatt] > NM

[jira] [Commented] (YARN-8574) Allow dot in attribute values

[ https://issues.apache.org/jira/browse/YARN-8574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559608#comment-16559608 ] Sunil Govindan commented on YARN-8574: -- I just rebased the branch. > Allow dot in attribute values

[jira] [Commented] (YARN-8574) Allow dot in attribute values

[ https://issues.apache.org/jira/browse/YARN-8574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559546#comment-16559546 ] Sunil Govindan commented on YARN-8574: -- Yes. Branch rebase is needed. > Allow dot in attribute

[jira] [Commented] (YARN-7863) Modify placement constraints to support node attributes

[ https://issues.apache.org/jira/browse/YARN-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558728#comment-16558728 ] Sunil Govindan commented on YARN-7863: -- Thanks [~Naganarasimha] and [~cheersyang] for comments A

[jira] [Commented] (YARN-8593) Add new RM web service endpoint to get cluster user info

[ https://issues.apache.org/jira/browse/YARN-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559713#comment-16559713 ] Sunil Govindan commented on YARN-8593: -- Yes. I also thought the same. But existing api {{public

[jira] [Commented] (YARN-8591) [ATSv2] NPE error while checking for entity acl in non-secure cluster

[ https://issues.apache.org/jira/browse/YARN-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559947#comment-16559947 ] Sunil Govindan commented on YARN-8591: -- Thanks [~rohithsharma]. This is a straight forward patch and

[jira] [Commented] (YARN-8606) Opportunistic scheduling doesnt work after failover

[ https://issues.apache.org/jira/browse/YARN-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564778#comment-16564778 ] Sunil Govindan commented on YARN-8606: -- Looks good to me as well. Committing shortly. >

[jira] [Commented] (YARN-8593) Add new RM web service endpoint to get cluster user info

[ https://issues.apache.org/jira/browse/YARN-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564675#comment-16564675 ] Sunil Govindan commented on YARN-8593: -- Thanks [~rohithsharma] for the details. You are correct. In a

[jira] [Commented] (YARN-8593) Add new RM web service endpoint to get cluster user info

[ https://issues.apache.org/jira/browse/YARN-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564804#comment-16564804 ] Sunil Govindan commented on YARN-8593: -- Sorry for some last minute comments. # Pls add detailed

[jira] [Updated] (YARN-8606) Opportunistic scheduling does not work post RM failover

[ https://issues.apache.org/jira/browse/YARN-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8606: - Summary: Opportunistic scheduling does not work post RM failover (was: Opportunistic scheduling

<    1   2   3   4   5   6   7   8   9   10   >