[jira] [Updated] (YARN-6061) Add a customized uncaughtexceptionhandler for critical threads in RM

[ https://issues.apache.org/jira/browse/YARN-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-6061: --- Attachment: YARN-6061.009.patch > Add a customized uncaughtexceptionhandler for critical threads in RM > --

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

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

[jira] [Commented] (YARN-6151) FS preemption does not consider child queues over fairshare if the parent is under

[ https://issues.apache.org/jira/browse/YARN-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860856#comment-15860856 ] Yufei Gu commented on YARN-6151: Thanks [~kasha] for the review and commit. > FS preempti

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

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

[jira] [Commented] (YARN-5889) Improve and refactor user-limit calculation in capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860851#comment-15860851 ] Sunil G commented on YARN-5889: --- Thanks for thorough reviews and commit [~leftnoteasy] , and

[jira] [Created] (YARN-6170) TimelineReaderServer should wait to join with HttpServer2

Sangjin Lee created YARN-6170: - Summary: TimelineReaderServer should wait to join with HttpServer2 Key: YARN-6170 URL: https://issues.apache.org/jira/browse/YARN-6170 Project: Hadoop YARN Issue T

[jira] [Commented] (YARN-6027) Improve /flows API for more flexible filters fromid, collapse, userid

[ https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860820#comment-15860820 ] Rohith Sharma K S commented on YARN-6027: - Thanks [~sjlee0] for summarizing! Could

[jira] [Commented] (YARN-5271) ATS client doesn't work with Jersey 2 on the classpath

[ https://issues.apache.org/jira/browse/YARN-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860760#comment-15860760 ] Weiwei Yang commented on YARN-5271: --- Thanks [~gtCarrera9], hi [~jojochuang] what's your t

[jira] [Commented] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860750#comment-15860750 ] Karthik Kambatla commented on YARN-6163: Patch that considers multiple RRs for an a

[jira] [Updated] (YARN-6163) FS Preemption is a trickle for severely starved applications

[ https://issues.apache.org/jira/browse/YARN-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6163: --- Attachment: yarn-6163-1.patch > FS Preemption is a trickle for severely starved applications >

[jira] [Commented] (YARN-5703) ReservationAgents are not correctly configured

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

[jira] [Commented] (YARN-6141) ppc64le on Linux doesn't trigger __linux get_executable codepath

[ https://issues.apache.org/jira/browse/YARN-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860687#comment-15860687 ] Sonia Garudi commented on YARN-6141: On upgrading the version of cmake to >3.1 the buil

[jira] [Commented] (YARN-6151) FS preemption does not consider child queues over fairshare if the parent is under

[ https://issues.apache.org/jira/browse/YARN-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860681#comment-15860681 ] Karthik Kambatla commented on YARN-6151: +1. Just committed this to branch-2.8. >

[jira] [Commented] (YARN-6151) FS preemption does not consider child queues over fairshare if the parent is under

[ https://issues.apache.org/jira/browse/YARN-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860682#comment-15860682 ] Karthik Kambatla commented on YARN-6151: Thanks for fixing this, Yufei. > FS pree

[jira] [Issue Comment Deleted] (YARN-6141) ppc64le on Linux doesn't trigger __linux get_executable codepath

[ https://issues.apache.org/jira/browse/YARN-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sonia Garudi updated YARN-6141: --- Comment: was deleted (was: On upgrading the version of cmake to >3.1 the build is successful. For cmak

[jira] [Updated] (YARN-6151) FS preemption does not consider child queues over fairshare if the parent is under

[ https://issues.apache.org/jira/browse/YARN-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6151: --- Summary: FS preemption does not consider child queues over fairshare if the parent is under (w

[jira] [Commented] (YARN-6141) ppc64le on Linux doesn't trigger __linux get_executable codepath

[ https://issues.apache.org/jira/browse/YARN-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860678#comment-15860678 ] Sonia Garudi commented on YARN-6141: On upgrading the version of cmake to >3.1 the buil

[jira] [Updated] (YARN-6156) AM blacklistdisableThreshold consider node partition count

[ https://issues.apache.org/jira/browse/YARN-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-6156: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4576 > AM blacklistdisableThreshold cons

[jira] [Commented] (YARN-6061) Add a customized uncaughtexceptionhandler for critical threads in RM

[ https://issues.apache.org/jira/browse/YARN-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860658#comment-15860658 ] ASF GitHub Bot commented on YARN-6061: -- Github user kambatla commented on a diff in th

[jira] [Commented] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860593#comment-15860593 ] Miklos Szegedi commented on YARN-3933: -- I could not repro the unit test issues above.

[jira] [Commented] (YARN-6169) container-executor message on empty configuration file can be improved

[ https://issues.apache.org/jira/browse/YARN-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860590#comment-15860590 ] Miklos Szegedi commented on YARN-6169: -- It would also be nice to print some additional

[jira] [Commented] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

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

[jira] [Updated] (YARN-6164) Expose maximum-am-resource-percent to Hadoop clients

[ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Qiu updated YARN-6164: - Description: To my knowledge, there is no way to programmatically obtain `yarn.scheduler.capacity.maximum-

[jira] [Updated] (YARN-6164) Expose maximum-am-resource-percent to Hadoop clients

[ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Qiu updated YARN-6164: - Target Version/s: 3.0.0-alpha3 > Expose maximum-am-resource-percent to Hadoop clients > ---

[jira] [Updated] (YARN-6164) Expose maximum-am-resource-percent to Hadoop clients

[ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Qiu updated YARN-6164: - Attachment: YARN-6164.001.patch > Expose maximum-am-resource-percent to Hadoop clients > --

[jira] [Commented] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

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

[jira] [Created] (YARN-6169) container-executor message on empty configuration file can be improved

Miklos Szegedi created YARN-6169: Summary: container-executor message on empty configuration file can be improved Key: YARN-6169 URL: https://issues.apache.org/jira/browse/YARN-6169 Project: Hadoop YA

[jira] [Commented] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860445#comment-15860445 ] Miklos Szegedi commented on YARN-6144: -- Thank you, [~kasha]. > FairScheduler: preempt

[jira] [Commented] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860443#comment-15860443 ] Hudson commented on YARN-6144: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #1122

[jira] [Commented] (YARN-6113) re-direct NM Web Service to get container logs for finished applications

[ https://issues.apache.org/jira/browse/YARN-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860436#comment-15860436 ] Xuan Gong commented on YARN-6113: - [~djp] The test case failure is not related > re-direct

[jira] [Updated] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-3933: - Attachment: YARN-3933.006.patch [~guoshiwei], thank you for looking into this. I ran into the same

[jira] [Commented] (YARN-5501) Container Pooling in YARN

[ https://issues.apache.org/jira/browse/YARN-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860407#comment-15860407 ] Hitesh Sharma commented on YARN-5501: - Thanks for the continued feedback, [~jlowe]. bq

[jira] [Updated] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6144: --- Fix Version/s: 3.0.0-alpha2 > FairScheduler: preempted resources can become negative >

[jira] [Updated] (YARN-6112) UpdateCallDuration is calculated only when debug logging is enabled

[ https://issues.apache.org/jira/browse/YARN-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6112: --- Fix Version/s: 3.0.0-alpha3 > UpdateCallDuration is calculated only when debug logging is enabl

[jira] [Updated] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6144: --- Fix Version/s: (was: 3.0.0-alpha2) 3.0.0-alpha3 > FairScheduler: preempt

[jira] [Updated] (YARN-6164) Expose maximum-am-resource-percent to Hadoop clients

[ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Qiu updated YARN-6164: - Description: To my knowledge, there is no way to programmatically obtain `yarn.scheduler.capacity.maximum-

[jira] [Created] (YARN-6168) Restarted RM may not inform AM about all existing containers

Billie Rinaldi created YARN-6168: Summary: Restarted RM may not inform AM about all existing containers Key: YARN-6168 URL: https://issues.apache.org/jira/browse/YARN-6168 Project: Hadoop YARN

[jira] [Commented] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860358#comment-15860358 ] Daniel Templeton commented on YARN-6166: LGTM. +1 Next, time, though, it's better

[jira] [Assigned] (YARN-3666) Federation Intercepting and propagating AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan reassigned YARN-3666: Assignee: Botong Huang (was: Kishore Chaliparambil) > Federation Intercepting and propagati

[jira] [Assigned] (YARN-5531) UnmanagedAM pool manager for federating application across clusters

[ https://issues.apache.org/jira/browse/YARN-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan reassigned YARN-5531: Assignee: Botong Huang (was: Sarvesh Sakalanaga) > UnmanagedAM pool manager for federating

[jira] [Commented] (YARN-6164) Expose maximum-am-resource-percent to Hadoop clients

[ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860357#comment-15860357 ] Benson Qiu commented on YARN-6164: -- I built the latest version of Hadoop and it appears th

[jira] [Commented] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860349#comment-15860349 ] Grant W commented on YARN-6166: --- I've taken another crack at the patch. Hopefully I don't co

[jira] [Created] (YARN-6167) RM option to delegate NM loss container action to AM

Billie Rinaldi created YARN-6167: Summary: RM option to delegate NM loss container action to AM Key: YARN-6167 URL: https://issues.apache.org/jira/browse/YARN-6167 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant W updated YARN-6166: -- Attachment: YARN-6166.patch > Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run > --

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant W updated YARN-6166: -- Attachment: (was: YARN-6166.patch) > Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run >

[jira] [Assigned] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton reassigned YARN-6166: -- Assignee: Grant W (was: haosdent) > Unnecessary INFO logs in AMRMClientAsyncImpl$Callba

[jira] [Commented] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860342#comment-15860342 ] Daniel Templeton commented on YARN-6166: I assigned the JIRA to you, [~genericuser]

[jira] [Commented] (YARN-6056) Yarn NM using LCE shows a failure when trying to delete a non-existing dir

[ https://issues.apache.org/jira/browse/YARN-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860337#comment-15860337 ] Jonathan Hung commented on YARN-6056: - Thanks [~varun_saxena]! Any update on this? > Y

[jira] [Commented] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860332#comment-15860332 ] Grant W commented on YARN-6166: --- [~haosd...@gmail.com] got pulled in from the previous issue

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant W updated YARN-6166: -- Attachment: YARN-6166.patch > Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run > --

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant W updated YARN-6166: -- Attachment: (was: YARN-6166.patch) > Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run >

[jira] [Comment Edited] (YARN-6158) FairScheduler: app usage can go to negative

[ https://issues.apache.org/jira/browse/YARN-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860301#comment-15860301 ] Miklos Szegedi edited comment on YARN-6158 at 2/9/17 10:18 PM: --

[jira] [Commented] (YARN-6144) FairScheduler: preempted resources can become negative

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

[jira] [Commented] (YARN-6158) FairScheduler: app usage can go to negative

[ https://issues.apache.org/jira/browse/YARN-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860301#comment-15860301 ] Miklos Szegedi commented on YARN-6158: -- I just noticed, think it is the same issue as

[jira] [Commented] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860277#comment-15860277 ] Daniel Templeton commented on YARN-6166: Thanks for the patch, [~haosd...@gmail.com

[jira] [Commented] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

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

[jira] [Commented] (YARN-6112) UpdateCallDuration is calculated only when debug logging is enabled

[ https://issues.apache.org/jira/browse/YARN-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860241#comment-15860241 ] Hudson commented on YARN-6112: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #1122

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-6166: --- Description: Logs like the following should be debug or else every legitimate stop causes unne

[jira] [Commented] (YARN-6112) UpdateCallDuration is calculated only when debug logging is enabled

[ https://issues.apache.org/jira/browse/YARN-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860212#comment-15860212 ] Yufei Gu commented on YARN-6112: Thanks [~kasha] for the review and commit. > UpdateCallDu

[jira] [Updated] (YARN-6112) UpdateCallDuration is calculated only when debug logging is enabled

[ https://issues.apache.org/jira/browse/YARN-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6112: --- Summary: UpdateCallDuration is calculated only when debug logging is enabled (was: fsOpDuratio

[jira] [Updated] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6144: - Attachment: YARN-6144.003.patch [~kasha], that is a good point. Updating patch. > FairScheduler: p

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant W updated YARN-6166: -- Attachment: YARN-6166.patch > Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run > --

[jira] [Commented] (YARN-6162) Cluster Writeable APIs in RM Rest APIs page refers to APIs as alpha but they are already in use with Spark

[ https://issues.apache.org/jira/browse/YARN-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860177#comment-15860177 ] Grant Sohn commented on YARN-6162: -- I'd say the APIs are stable enough that they shouldn't

[jira] [Commented] (YARN-4675) Reorganize TimelineClient and TimelineClientImpl into separate classes for ATSv1.x and ATSv2

[ https://issues.apache.org/jira/browse/YARN-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860164#comment-15860164 ] Sangjin Lee commented on YARN-4675: --- We should be good to go once you addressed Varun's c

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Whiteheart updated YARN-6166: --- Description: Logs like the following should be debug or else every legitimate stop causes unne

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Whiteheart updated YARN-6166: --- Fix Version/s: (was: 2.3.0) > Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerT

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Whiteheart updated YARN-6166: --- Affects Version/s: (was: 2.3.0) (was: 2.2.0)

[jira] [Updated] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Whiteheart updated YARN-6166: --- Target Version/s: 2.7.4 (was: 2.3.0) > Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHa

[jira] [Commented] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

[ https://issues.apache.org/jira/browse/YARN-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860138#comment-15860138 ] Grant Whiteheart commented on YARN-6166: YARN-1022 fixed unnecessary log messages f

[jira] [Commented] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860136#comment-15860136 ] Sangjin Lee commented on YARN-4985: --- Thanks for refreshing my memory on this Haibo. Yes,

[jira] [Created] (YARN-6166) Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run

Grant Whiteheart created YARN-6166: -- Summary: Unnecessary INFO logs in AMRMClientAsyncImpl$CallbackHandlerThread.run Key: YARN-6166 URL: https://issues.apache.org/jira/browse/YARN-6166 Project: Hadoo

[jira] [Commented] (YARN-6027) Improve /flows API for more flexible filters fromid, collapse, userid

[ https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860111#comment-15860111 ] Sangjin Lee commented on YARN-6027: --- We discussed this offline during our status call. Ju

[jira] [Commented] (YARN-6162) Cluster Writeable APIs in RM Rest APIs page refers to APIs as alpha but they are already in use with Spark

[ https://issues.apache.org/jira/browse/YARN-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860079#comment-15860079 ] Daniel Templeton commented on YARN-6162: Is the issue that the APIs are mislabeled

[jira] [Commented] (YARN-6158) FairScheduler: app usage can go to negative

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

[jira] [Commented] (YARN-4090) Make Collections.sort() more efficient in FSParentQueue.java

[ https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860008#comment-15860008 ] Yufei Gu commented on YARN-4090: Thanks [~zsl2007]. I think you get it covered. Things migh

[jira] [Commented] (YARN-5889) Improve and refactor user-limit calculation in capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859996#comment-15859996 ] Hudson commented on YARN-5889: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #1122

[jira] [Assigned] (YARN-6165) Intra-queue preemption occurs even when preemption is turned off for a specific queue.

[ https://issues.apache.org/jira/browse/YARN-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne reassigned YARN-6165: Assignee: Eric Payne > Intra-queue preemption occurs even when preemption is turned off for a > spe

[jira] [Commented] (YARN-6165) Intra-queue preemption occurs even when preemption is turned off for a specific queue.

[ https://issues.apache.org/jira/browse/YARN-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859987#comment-15859987 ] Eric Payne commented on YARN-6165: -- Use Case: - Configure queues with cluster-wide preempt

[jira] [Updated] (YARN-5889) Improve and refactor user-limit calculation in capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-5889: - Summary: Improve and refactor user-limit calculation in capacity scheduler (was: Improve user-limit calcul

[jira] [Updated] (YARN-6158) FairScheduler: app usage can go to negative

[ https://issues.apache.org/jira/browse/YARN-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6158: - Attachment: YARN-6158.000.patch Attaching patch. > FairScheduler: app usage can go to negative > -

[jira] [Created] (YARN-6165) Intra-queue preemption occurs even when preemption is turned off for a specific queue.

Eric Payne created YARN-6165: Summary: Intra-queue preemption occurs even when preemption is turned off for a specific queue. Key: YARN-6165 URL: https://issues.apache.org/jira/browse/YARN-6165 Project: H

[jira] [Commented] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859912#comment-15859912 ] Haibo Chen commented on YARN-4985: -- The dependency is not mainly because all tests are in

[jira] [Resolved] (YARN-5700) testAMRestartNotLostContainerCompleteMsg times out intermittently in 2.8

[ https://issues.apache.org/jira/browse/YARN-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger resolved YARN-5700. --- Resolution: Cannot Reproduce Revisited this and I cannot reproduce the failure. Closing as cannot repro

[jira] [Commented] (YARN-5956) Refactor ClientRMService

[ https://issues.apache.org/jira/browse/YARN-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859779#comment-15859779 ] Sunil G commented on YARN-5956: --- Thanks [~lewuathe]. Were u mentioning about {{YARN-5956.08.

[jira] [Commented] (YARN-5501) Container Pooling in YARN

[ https://issues.apache.org/jira/browse/YARN-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859587#comment-15859587 ] Jason Lowe commented on YARN-5501: -- Thanks for the detailed answers. I highly recommend t

[jira] [Commented] (YARN-5956) Refactor ClientRMService

[ https://issues.apache.org/jira/browse/YARN-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859464#comment-15859464 ] Kai Sasaki commented on YARN-5956: -- [~sunilg] Sorry for late. I checked redundant {{checkA

[jira] [Commented] (YARN-6113) re-direct NM Web Service to get container logs for finished applications

[ https://issues.apache.org/jira/browse/YARN-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859421#comment-15859421 ] Junping Du commented on YARN-6113: -- Thanks Xuan for updating the patch. Latest patch LGTM.

[jira] [Commented] (YARN-6027) Improve /flows API for more flexible filters fromid, collapse, userid

[ https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859344#comment-15859344 ] Varun Saxena commented on YARN-6027: Ok...I had forgotton that we currently do not limi

[jira] [Commented] (YARN-6157) Inconsistencies in verifying Max Applications

[ https://issues.apache.org/jira/browse/YARN-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859205#comment-15859205 ] Varun Saxena commented on YARN-6157: [~Naganarasimha], the check for system max apps is