[jira] [Updated] (YARN-9873) Mutation API Config Change updates Version Number

[ https://issues.apache.org/jira/browse/YARN-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9873: - Summary: Mutation API Config Change updates Version Number (was: Version Number for each

[jira] [Commented] (YARN-9772) CapacitySchedulerQueueManager has incorrect list of queues

[ https://issues.apache.org/jira/browse/YARN-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933593#comment-16933593 ] Sunil Govindan commented on YARN-9772: -- Thanks. I think the point made by [~tarunparimi] is valid.

[jira] [Commented] (YARN-9617) RM UI enables viewing pages using Timeline Reader for a user who can not access the YARN config endpoint

[ https://issues.apache.org/jira/browse/YARN-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933375#comment-16933375 ] Sunil Govindan commented on YARN-9617: -- [~akhilpb] cud u pls add a validation for this case? > RM UI

[jira] [Commented] (YARN-9766) YARN CapacityScheduler QueueMetrics has missing metrics for parent queues having same name

[ https://issues.apache.org/jira/browse/YARN-9766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933372#comment-16933372 ] Sunil Govindan commented on YARN-9766: -- [~tarunparimi] [~Prabhu Joseph] I went through the fix. I

[jira] [Commented] (YARN-9814) JobHistoryServer can't delete aggregated files, if remote app root directory is created by NodeManager

[ https://issues.apache.org/jira/browse/YARN-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932026#comment-16932026 ] Sunil Govindan commented on YARN-9814: -- I have committed this to trunk, thanks . [~adam.antal] If

[jira] [Commented] (YARN-9814) JobHistoryServer can't delete aggregated files, if remote app root directory is created by NodeManager

[ https://issues.apache.org/jira/browse/YARN-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932022#comment-16932022 ] Sunil Govindan commented on YARN-9814: -- +1 Committing shortly > JobHistoryServer can't delete

[jira] [Updated] (YARN-9833) Race condition when DirectoryCollection.checkDirs() runs during container launch

[ https://issues.apache.org/jira/browse/YARN-9833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9833: - Fix Version/s: 3.1.4 3.2.2 > Race condition when

[jira] [Commented] (YARN-9833) Race condition when DirectoryCollection.checkDirs() runs during container launch

[ https://issues.apache.org/jira/browse/YARN-9833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931493#comment-16931493 ] Sunil Govindan commented on YARN-9833: -- +1. Committing this now. > Race condition when

[jira] [Commented] (YARN-9838) Using the CapacityScheduler,Apply "movetoqueue" on the application which CS reserved containers for,will cause "Num Container" and "Used Resource" in ResourceUsage metri

[ https://issues.apache.org/jira/browse/YARN-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931192#comment-16931192 ] Sunil Govindan commented on YARN-9838: -- [~jiulongZhu] Thanks for reporting this issues. Few general

[jira] [Commented] (YARN-9814) JobHistoryServer can't delete aggregated files, if remote app root directory is created by NodeManager

[ https://issues.apache.org/jira/browse/YARN-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930281#comment-16930281 ] Sunil Govindan commented on YARN-9814: -- Thanks [~adam.antal]. This approach looks fine to me.

[jira] [Commented] (YARN-9674) Max AM Resource calculation is wrong

[ https://issues.apache.org/jira/browse/YARN-9674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927303#comment-16927303 ] Sunil Govindan commented on YARN-9674: -- Across partitions, it should be same behaviour. Looks like a

[jira] [Commented] (YARN-9813) RM does not start on JDK11 when UIv2 is enabled

[ https://issues.apache.org/jira/browse/YARN-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924052#comment-16924052 ] Sunil Govindan commented on YARN-9813: -- pending jenkins > RM does not start on JDK11 when UIv2 is

[jira] [Commented] (YARN-9813) RM does not start on JDK11 when UIv2 is enabled

[ https://issues.apache.org/jira/browse/YARN-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924041#comment-16924041 ] Sunil Govindan commented on YARN-9813: -- Thanks [~adam.antal]  I ll test this and let know whether it

[jira] [Commented] (YARN-7055) YARN Timeline Service v.2: beta 1 / GA

[ https://issues.apache.org/jira/browse/YARN-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923857#comment-16923857 ] Sunil Govindan commented on YARN-7055: -- Kudos! Thanks to all the contributors who helped in ATSv2. 

[jira] [Commented] (YARN-9804) Update ATSv2 document for latest feature supports

[ https://issues.apache.org/jira/browse/YARN-9804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922320#comment-16922320 ] Sunil Govindan commented on YARN-9804: -- +1. Thanks [~rohithsharma] > Update ATSv2 document for

[jira] [Commented] (YARN-9797) LeafQueue#activateApplications should use resourceCalculator#fitsIn

[ https://issues.apache.org/jira/browse/YARN-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921139#comment-16921139 ] Sunil Govindan commented on YARN-9797: -- +1. > LeafQueue#activateApplications should use

[jira] [Commented] (YARN-9784) org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestLeafQueue is flaky

[ https://issues.apache.org/jira/browse/YARN-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921127#comment-16921127 ] Sunil Govindan commented on YARN-9784: -- +1 I ll commit this shortly. Thanks [~kmarton] >

[jira] [Commented] (YARN-9785) Fix DominantResourceCalculator when one resource is zero

[ https://issues.apache.org/jira/browse/YARN-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921103#comment-16921103 ] Sunil Govindan commented on YARN-9785: -- +1 from me as well. Lets get this in. > Fix

[jira] [Commented] (YARN-9785) Fix DominantResourceCalculator when one resource is zero

[ https://issues.apache.org/jira/browse/YARN-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918445#comment-16918445 ] Sunil Govindan commented on YARN-9785: -- Thanks [~bibinchundatt] > Fix DominantResourceCalculator

[jira] [Comment Edited] (YARN-9785) Fix DominantResourceCalculator when one resource is zero

[ https://issues.apache.org/jira/browse/YARN-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918310#comment-16918310 ] Sunil Govindan edited comment on YARN-9785 at 8/29/19 6:05 AM: --- Thanks

[jira] [Commented] (YARN-9785) Fix DominantResourceCalculator when one resource is zero

[ https://issues.apache.org/jira/browse/YARN-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918310#comment-16918310 ] Sunil Govindan commented on YARN-9785: -- Thanks [~bibinchundatt] for helping to clarify the issues. As

[jira] [Commented] (YARN-9785) Application gets activated even when AM memory has reached

[ https://issues.apache.org/jira/browse/YARN-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917919#comment-16917919 ] Sunil Govindan commented on YARN-9785: -- Thanks [~bibinchundatt] for detailed analysis. I am checking

[jira] [Commented] (YARN-9785) Application gets activated even when AM memory has reached

[ https://issues.apache.org/jira/browse/YARN-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917628#comment-16917628 ] Sunil Govindan commented on YARN-9785: -- [~BilwaST] [~bibinchundatt] We were trying a different

[jira] [Updated] (YARN-9785) Application gets activated even when AM memory has reached

[ https://issues.apache.org/jira/browse/YARN-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9785: - Attachment: YARN-9785.wip.patch > Application gets activated even when AM memory has reached >

[jira] [Commented] (YARN-9642) AbstractYarnScheduler#clearPendingContainerCache could run even after transitiontostandby

[ https://issues.apache.org/jira/browse/YARN-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912313#comment-16912313 ] Sunil Govindan commented on YARN-9642: -- +1 on latest patch. [~bibinchundatt] pls feel free to get

[jira] [Updated] (YARN-9758) Upgrade JQuery to latest version for YARN UI

[ https://issues.apache.org/jira/browse/YARN-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9758: - Summary: Upgrade JQuery to latest version for YARN UI (was: Upgrade JQuery to latest version for

[jira] [Commented] (YARN-9758) Upgrade JQuery to latest version for YARN

[ https://issues.apache.org/jira/browse/YARN-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911327#comment-16911327 ] Sunil Govindan commented on YARN-9758: -- +1 Committing shortly > Upgrade JQuery to latest version

[jira] [Commented] (YARN-6492) Generate queue metrics for each partition

[ https://issues.apache.org/jira/browse/YARN-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909635#comment-16909635 ] Sunil Govindan commented on YARN-6492: -- I agree with [~eepayne] point in splitting this. So it will

[jira] [Commented] (YARN-2599) Standby RM should expose jmx endpoint

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909634#comment-16909634 ] Sunil Govindan commented on YARN-2599: -- Thanks folks. Committed to trunk > Standby RM should expose

[jira] [Updated] (YARN-2599) Standby RM should expose jmx endpoint

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-2599: - Summary: Standby RM should expose jmx endpoint (was: Standby RM should also expose some jmx and

[jira] [Commented] (YARN-2599) Standby RM should also expose some jmx and metrics

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909039#comment-16909039 ] Sunil Govindan commented on YARN-2599: -- Thanks [~cheersyang] for the review. Thanks [~rohithsharma]

[jira] [Updated] (YARN-2599) Standby RM should also expose some jmx and metrics

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-2599: - Release Note: YARN /jmx URL end points will be accessible per resource manager process. Hence

[jira] [Commented] (YARN-2599) Standby RM should also expose some jmx and metrics

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908779#comment-16908779 ] Sunil Govindan commented on YARN-2599: -- cc [~cheersyang] New patch is added. > Standby RM should

[jira] [Updated] (YARN-2599) Standby RM should also expose some jmx and metrics

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-2599: - Attachment: YARN-2599.002.patch > Standby RM should also expose some jmx and metrics >

[jira] [Commented] (YARN-2599) Standby RM should also expose some jmx and metrics

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907389#comment-16907389 ] Sunil Govindan commented on YARN-2599: -- Thanks [~bibinchundatt] I do not think its a compatibility

[jira] [Commented] (YARN-2599) Standby RM should also expose some jmx and metrics

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907100#comment-16907100 ] Sunil Govindan commented on YARN-2599: -- Kicking this again. Having per process jmx is always better

[jira] [Commented] (YARN-9106) Add option to graceful decommission to not wait for applications

[ https://issues.apache.org/jira/browse/YARN-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906857#comment-16906857 ] Sunil Govindan commented on YARN-9106: -- cc [~leftnoteasy] [~tangzhankun] > Add option to graceful

[jira] [Commented] (YARN-9106) Add option to graceful decommission to not wait for applications

[ https://issues.apache.org/jira/browse/YARN-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906856#comment-16906856 ] Sunil Govindan commented on YARN-9106: -- wait-for-applications and wait-for-app-masters Expecting

[jira] [Commented] (YARN-9738) Remove lock on ClusterNodeTracker#getNodeReport as it blocks application submission

[ https://issues.apache.org/jira/browse/YARN-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905952#comment-16905952 ] Sunil Govindan commented on YARN-9738: -- Hi [~BilwaST] {{nodes}} is operated under read and write

[jira] [Updated] (YARN-9729) [UI2] Fix error message for logs when ATSv2 is offline

[ https://issues.apache.org/jira/browse/YARN-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9729: - Summary: [UI2] Fix error message for logs when ATSv2 is offline (was: [UI2] Fix error message

[jira] [Commented] (YARN-9729) [UI2] Fix error message for logs without ATSv2

[ https://issues.apache.org/jira/browse/YARN-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904468#comment-16904468 ] Sunil Govindan commented on YARN-9729: -- Addressed comments from Akhil. Thanks [~zsiegl] and

[jira] [Updated] (YARN-9729) [UI2] Fix error message for logs without ATSv2

[ https://issues.apache.org/jira/browse/YARN-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9729: - Attachment: YARN-9729.003.patch > [UI2] Fix error message for logs without ATSv2 >

[jira] [Commented] (YARN-9729) [UI2] Fix error message for logs without ATSv2

[ https://issues.apache.org/jira/browse/YARN-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904459#comment-16904459 ] Sunil Govindan commented on YARN-9729: -- Mistakenly pushed wrong patch. Reverted same.   > [UI2] Fix

[jira] [Updated] (YARN-9729) [UI2] Fix error message for logs without ATSv2

[ https://issues.apache.org/jira/browse/YARN-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9729: - Attachment: YARN-9729.002.patch > [UI2] Fix error message for logs without ATSv2 >

[jira] [Commented] (YARN-9701) Yarn service cli commands do not connect to ssl enabled RM using ssl-client.xml configs

[ https://issues.apache.org/jira/browse/YARN-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904346#comment-16904346 ] Sunil Govindan commented on YARN-9701: -- cc [~billie.rina...@gmail.com] > Yarn service cli commands

[jira] [Updated] (YARN-9715) [UI2] yarn-container-log URI need to be encoded to avoid potential misuses

[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9715: - Summary: [UI2] yarn-container-log URI need to be encoded to avoid potential misuses (was: [YARN

[jira] [Commented] (YARN-9715) [YARN UI2] yarn-container-log support for https Knox Gateway url in nodes page

[ https://issues.apache.org/jira/browse/YARN-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903615#comment-16903615 ] Sunil Govindan commented on YARN-9715: -- +1 Committing this in. > [YARN UI2] yarn-container-log

[jira] [Commented] (YARN-9721) An easy method to exclude a nodemanager from the yarn cluster cleanly

[ https://issues.apache.org/jira/browse/YARN-9721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900661#comment-16900661 ] Sunil Govindan commented on YARN-9721: -- Looping [~tangzhankun] to this thread. [~yuan_zac], ideally

[jira] [Commented] (YARN-9722) PlacementRule logs object ID in place of queue name.

[ https://issues.apache.org/jira/browse/YARN-9722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900621#comment-16900621 ] Sunil Govindan commented on YARN-9722: -- Looks fine, lets get this in. +1 > PlacementRule logs object

[jira] [Commented] (YARN-9583) Failed job which is submitted unknown queue is showed all users

[ https://issues.apache.org/jira/browse/YARN-9583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900619#comment-16900619 ] Sunil Govindan commented on YARN-9583: -- Thanks [~magnum] [~Prabhu Joseph] and [~magnum], i am

[jira] [Commented] (YARN-9687) Queue headroom check may let unacceptable allocation off when using DominantResourceCalculator

[ https://issues.apache.org/jira/browse/YARN-9687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890322#comment-16890322 ] Sunil Govindan commented on YARN-9687: -- Hi [~Tao Yang] Thanks for reporting this issue. Yes, we have

[jira] [Commented] (YARN-9681) AM resource limit is incorrect for queue

[ https://issues.apache.org/jira/browse/YARN-9681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885987#comment-16885987 ] Sunil Govindan commented on YARN-9681: -- Hi [~gb.ana...@gmail.com] cud u pls share more details on

[jira] [Commented] (YARN-9642) AbstractYarnScheduler#clearPendingContainerCache could run even after transitiontostandby

[ https://issues.apache.org/jira/browse/YARN-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878985#comment-16878985 ] Sunil Govindan commented on YARN-9642: -- +1. from me. Committing shortly if no objections. >

[jira] [Comment Edited] (YARN-9662) Preemption not working on NodeLabels

[ https://issues.apache.org/jira/browse/YARN-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877538#comment-16877538 ] Sunil Govindan edited comment on YARN-9662 at 7/3/19 7:01 AM: -- [~Amithsha]

[jira] [Commented] (YARN-9662) Preemption not working on NodeLabels

[ https://issues.apache.org/jira/browse/YARN-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877538#comment-16877538 ] Sunil Govindan commented on YARN-9662: -- [~Amithsha] hadoop-2.7 doesnt support label based preemption,

[jira] [Commented] (YARN-9644) First RMContext object is always leaked during switch over

[ https://issues.apache.org/jira/browse/YARN-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877536#comment-16877536 ] Sunil Govindan commented on YARN-9644: -- [~bibinchundatt] cud u pls share 3.2 patch > First RMContext

[jira] [Commented] (YARN-7621) Support submitting apps with queue path for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877534#comment-16877534 ] Sunil Govindan commented on YARN-7621: -- I think this makes sense to me.  We are trimming the last

[jira] [Commented] (YARN-9629) Support configurable MIN_LOG_ROLLING_INTERVAL

[ https://issues.apache.org/jira/browse/YARN-9629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877018#comment-16877018 ] Sunil Govindan commented on YARN-9629: -- Thanks [~adam.antal] First point makes sense if the default

[jira] [Commented] (YARN-9644) First RMContext object is always leaked during switch over

[ https://issues.apache.org/jira/browse/YARN-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876730#comment-16876730 ] Sunil Govindan commented on YARN-9644: -- Thanks [~bibinchundatt]. Pushed to trunk. Conflicts in

[jira] [Updated] (YARN-9644) First RMContext object is always leaked during switch over

[ https://issues.apache.org/jira/browse/YARN-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9644: - Summary: First RMContext object is always leaked during switch over (was: First RMContext always

[jira] [Updated] (YARN-9327) Improve synchronisation in ProtoUtils#convertToProtoFormat block

[ https://issues.apache.org/jira/browse/YARN-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9327: - Summary: Improve synchronisation in ProtoUtils#convertToProtoFormat block (was:

[jira] [Commented] (YARN-9327) ProtoUtils#convertToProtoFormat block Application Master Service and many more

[ https://issues.apache.org/jira/browse/YARN-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876694#comment-16876694 ] Sunil Govindan commented on YARN-9327: -- +1, Committing shortly. > ProtoUtils#convertToProtoFormat

[jira] [Commented] (YARN-9629) Support configurable MIN_LOG_ROLLING_INTERVAL

[ https://issues.apache.org/jira/browse/YARN-9629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876693#comment-16876693 ] Sunil Govindan commented on YARN-9629: -- Hi [~adam.antal]  Thanks for the patch. Couple of minor

[jira] [Commented] (YARN-9644) First RMContext always leaked during switch over

[ https://issues.apache.org/jira/browse/YARN-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873005#comment-16873005 ] Sunil Govindan commented on YARN-9644: -- +1 on this patch. Fix seems fine for both cases which is

[jira] [Commented] (YARN-9639) DecommissioningNodesWatcher cause memory leak

[ https://issues.apache.org/jira/browse/YARN-9639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872922#comment-16872922 ] Sunil Govindan commented on YARN-9639: -- Thanks [~BilwaST] for pointing out. I have seen once, when

[jira] [Assigned] (YARN-7721) TestContinuousScheduling fails sporadically with NPE

[ https://issues.apache.org/jira/browse/YARN-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan reassigned YARN-7721: Assignee: Sunil Govindan (was: Wilfred Spiegelenburg) > TestContinuousScheduling fails

[jira] [Commented] (YARN-9639) DecommissioningNodesWatcher cause memory leak

[ https://issues.apache.org/jira/browse/YARN-9639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872174#comment-16872174 ] Sunil Govindan commented on YARN-9639: -- [~bibinchundatt] a quick question. is it better to have a

[jira] [Commented] (YARN-9635) Nodes page displayed duplicate nodes

[ https://issues.apache.org/jira/browse/YARN-9635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872010#comment-16872010 ] Sunil Govindan commented on YARN-9635: -- Hi [~jiwq] and [~Tao Yang] I am trying to understand whether

[jira] [Commented] (YARN-9639) DecommissioningNodesWatcher cause memory leak

[ https://issues.apache.org/jira/browse/YARN-9639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870594#comment-16870594 ] Sunil Govindan commented on YARN-9639: -- One small nit, In DecommissioningNodesWatcher, Do we need to

[jira] [Commented] (YARN-9642) AbstractYarnScheduler#clearPendingContainerCache could run even after transitiontostandby

[ https://issues.apache.org/jira/browse/YARN-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870425#comment-16870425 ] Sunil Govindan commented on YARN-9642: -- Good catch. Yes, this timer ideally need to be cancelled for

[jira] [Commented] (YARN-9327) ProtoUtils#convertToProtoFormat block Application Master Service and many more

[ https://issues.apache.org/jira/browse/YARN-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869689#comment-16869689 ] Sunil Govindan commented on YARN-9327: -- looks fine to me. [~wangda] cud u pls take a look.  if no

[jira] [Commented] (YARN-9625) UI2 - No link to a queue on the Queues page for Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863925#comment-16863925 ] Sunil Govindan commented on YARN-9625: -- + [~zsiegl] [~snemeth] > UI2 - No link to a queue on the

[jira] [Commented] (YARN-9626) UI2 - Fair scheduler queue apps page issues

[ https://issues.apache.org/jira/browse/YARN-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863926#comment-16863926 ] Sunil Govindan commented on YARN-9626: -- + [~snemeth] [~zsiegl] > UI2 - Fair scheduler queue apps

[jira] [Commented] (YARN-9607) Auto-configuring rollover-size of IFile format for non-appendable filesystems

[ https://issues.apache.org/jira/browse/YARN-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862164#comment-16862164 ] Sunil Govindan commented on YARN-9607: -- Hi [~adam.antal] Could we add a new config which says

[jira] [Commented] (YARN-9327) ProtoUtils#convertToProtoFormat block Application Master Service and many more

[ https://issues.apache.org/jira/browse/YARN-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862153#comment-16862153 ] Sunil Govindan commented on YARN-9327: -- This is a good catch. I have seen in some other proto class

[jira] [Commented] (YARN-9545) Create healthcheck REST endpoint for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862121#comment-16862121 ] Sunil Govindan commented on YARN-9545: -- Corrected and committed patch w/o the hidden dir which caused

[jira] [Commented] (YARN-9545) Create healthcheck REST endpoint for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862112#comment-16862112 ] Sunil Govindan commented on YARN-9545: -- Hi [~ste...@apache.org], you are correct. Its a mistake

[jira] [Commented] (YARN-9573) DistributedShell cannot specify LogAggregationContext

[ https://issues.apache.org/jira/browse/YARN-9573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16857468#comment-16857468 ] Sunil Govindan commented on YARN-9573: -- back ported to trunk cud u pls help to backport to

[jira] [Commented] (YARN-9573) DistributedShell cannot specify LogAggregationContext

[ https://issues.apache.org/jira/browse/YARN-9573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855746#comment-16855746 ] Sunil Govindan commented on YARN-9573: -- Thanks [~adam.antal] I definitely would love to see removal

[jira] [Commented] (YARN-8906) [UI2] NM hostnames not displayed correctly in Node Heatmap Chart

[ https://issues.apache.org/jira/browse/YARN-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854440#comment-16854440 ] Sunil Govindan commented on YARN-8906: -- Thanks [~akhilpb] > [UI2] NM hostnames not displayed

[jira] [Commented] (YARN-8906) [UI2] NM hostnames not displayed correctly in Node Heatmap Chart

[ https://issues.apache.org/jira/browse/YARN-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854439#comment-16854439 ] Sunil Govindan commented on YARN-8906: -- +1 > [UI2] NM hostnames not displayed correctly in Node

[jira] [Commented] (YARN-9545) Create healthcheck REST endpoint for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852793#comment-16852793 ] Sunil Govindan commented on YARN-9545: -- Thanks [~snemeth] for the thoughts. YARN-9016 need not have

[jira] [Commented] (YARN-9543) [UI2] Handle ATSv2 server down or failures cases gracefully in YARN UI v2

[ https://issues.apache.org/jira/browse/YARN-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852722#comment-16852722 ] Sunil Govindan commented on YARN-9543: -- Committed to trunk. I ll backport to 3.2 and 3.1 when

[jira] [Updated] (YARN-9543) [UI2] Handle ATSv2 server down or failures cases gracefully in YARN UI v2

[ https://issues.apache.org/jira/browse/YARN-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9543: - Summary: [UI2] Handle ATSv2 server down or failures cases gracefully in YARN UI v2 (was: UI2

[jira] [Commented] (YARN-9545) Create healthcheck REST endpoint for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852662#comment-16852662 ] Sunil Govindan commented on YARN-9545: -- This patch is committed to trunk. branch-3.2 is failing, Cud

[jira] [Commented] (YARN-9033) ResourceHandlerChain#bootstrap is invoked twice during NM start if LinuxContainerExecutor enabled

[ https://issues.apache.org/jira/browse/YARN-9033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852655#comment-16852655 ] Sunil Govindan commented on YARN-9033: -- Looks good to me. +1   > ResourceHandlerChain#bootstrap is

[jira] [Commented] (YARN-9545) Create healthcheck REST endpoint for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852102#comment-16852102 ] Sunil Govindan commented on YARN-9545: -- Thanks [~zsiegl], lets go with this approach. Committing

[jira] [Updated] (YARN-9452) Fix TestDistributedShell and TestTimelineAuthFilterForV2 failures

[ https://issues.apache.org/jira/browse/YARN-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9452: - Summary: Fix TestDistributedShell and TestTimelineAuthFilterForV2 failures (was: Fix failing

[jira] [Commented] (YARN-9452) Fix failing testcases TestDistributedShell and TestTimelineAuthFilterForV2

[ https://issues.apache.org/jira/browse/YARN-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852076#comment-16852076 ] Sunil Govindan commented on YARN-9452: -- +1 on latest patch.  Committing now. > Fix failing

[jira] [Commented] (YARN-9525) IFile format is not working against s3a remote folder

[ https://issues.apache.org/jira/browse/YARN-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851569#comment-16851569 ] Sunil Govindan commented on YARN-9525: -- [~adam.antal] are we planning to fix nagative offset error

[jira] [Commented] (YARN-9482) DistributedShell job with localization fails in unsecure cluster

[ https://issues.apache.org/jira/browse/YARN-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848940#comment-16848940 ] Sunil Govindan commented on YARN-9482: -- Thanks [~giovanni.fumarola], [~Prabhu Joseph] and [~pbacsko]

[jira] [Commented] (YARN-9543) UI2 should handle missing ATSv2 gracefully

[ https://issues.apache.org/jira/browse/YARN-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848936#comment-16848936 ] Sunil Govindan commented on YARN-9543: -- Getting this in now. Thanks [~zsiegl] and [~akhilpb]   >

[jira] [Commented] (YARN-9545) Create healthcheck REST endpoint for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848935#comment-16848935 ] Sunil Govindan commented on YARN-9545: -- Thanks [~zsiegl], in general the DAO class looks good and

[jira] [Commented] (YARN-9543) UI2 should handle missing ATSv2 gracefully

[ https://issues.apache.org/jira/browse/YARN-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846695#comment-16846695 ] Sunil Govindan commented on YARN-9543: -- Patch looks good to me. [~zsiegl] could you also pls cross

[jira] [Commented] (YARN-9545) Create healthcheck REST endpoint for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846694#comment-16846694 ] Sunil Govindan commented on YARN-9545: -- [~zsiegl] cud u pls check the find bugs warnings? > Create

[jira] [Updated] (YARN-9546) Add configuration option for YARN Native services AM classpath

[ https://issues.apache.org/jira/browse/YARN-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9546: - Summary: Add configuration option for YARN Native services AM classpath (was: Add configuration

[jira] [Commented] (YARN-9546) Add configuration option for yarn services AM classpath

[ https://issues.apache.org/jira/browse/YARN-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844017#comment-16844017 ] Sunil Govindan commented on YARN-9546: -- +1 on latest patch. Committing same. > Add configuration

[jira] [Updated] (YARN-9519) TFile log aggregation file format is not working for yarn.log-aggregation.TFile.remote-app-log-dir config

[ https://issues.apache.org/jira/browse/YARN-9519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-9519: - Summary: TFile log aggregation file format is not working for

[jira] [Commented] (YARN-9546) Add configuration option for yarn services AM classpath

[ https://issues.apache.org/jira/browse/YARN-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838142#comment-16838142 ] Sunil Govindan commented on YARN-9546: -- Hi [~shuzirra] As per this patch, you are introducing a new

[jira] [Commented] (YARN-9545) Create healthcheck REST endpoint for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837318#comment-16837318 ] Sunil Govindan commented on YARN-9545: -- Thanks [~Prabhu Joseph] for the thoughts. In minimum level,

  1   2   3   4   5   6   7   8   9   10   >