[jira] [Commented] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

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

[jira] [Commented] (YARN-4376) Memory Timeline Store return incorrect results on fromId paging

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

[jira] [Updated] (YARN-4480) Clean up some inappropriate imports

[ https://issues.apache.org/jira/browse/YARN-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Zheng updated YARN-4480: Attachment: YARN-4480-v1.patch Uploaded a patch to do the clean up. > Clean up some inappropriate imports >

[jira] [Commented] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

[ https://issues.apache.org/jira/browse/YARN-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063767#comment-15063767 ] Tao Jie commented on YARN-4477: --- Add one test case. > FairScheduler: encounter infinite loop in

[jira] [Commented] (YARN-2934) Improve handling of container's stderr

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

[jira] [Created] (YARN-4480) Clean up some inappropriate imports

Kai Zheng created YARN-4480: --- Summary: Clean up some inappropriate imports Key: YARN-4480 URL: https://issues.apache.org/jira/browse/YARN-4480 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

[ https://issues.apache.org/jira/browse/YARN-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated YARN-4477: -- Attachment: YARN-4477.002.patch > FairScheduler: encounter infinite loop in attemptScheduling >

[jira] [Updated] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

[ https://issues.apache.org/jira/browse/YARN-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated YARN-4477: -- Attachment: YARN-4477.003.patch > FairScheduler: encounter infinite loop in attemptScheduling >

[jira] [Updated] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

[ https://issues.apache.org/jira/browse/YARN-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated YARN-4477: -- Attachment: YARN-4477.003.patch > FairScheduler: encounter infinite loop in attemptScheduling >

[jira] [Updated] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

[ https://issues.apache.org/jira/browse/YARN-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated YARN-4477: -- Attachment: (was: YARN-4477.003.patch) > FairScheduler: encounter infinite loop in attemptScheduling >

[jira] [Updated] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

[ https://issues.apache.org/jira/browse/YARN-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated YARN-4477: -- Attachment: (was: YARN-4477.003.patch) > FairScheduler: encounter infinite loop in attemptScheduling >

[jira] [Updated] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

[ https://issues.apache.org/jira/browse/YARN-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated YARN-4477: -- Attachment: YARN-4477.003.patch > FairScheduler: encounter infinite loop in attemptScheduling >

[jira] [Commented] (YARN-4463) Container launch failure when yarn.nodemanager.log-dirs directory path contains space

[ https://issues.apache.org/jira/browse/YARN-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063818#comment-15063818 ] Bibin A Chundatt commented on YARN-4463: Hi [~sunilg] To explain the problem further. In

[jira] [Commented] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

[ https://issues.apache.org/jira/browse/YARN-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063820#comment-15063820 ] Tao Jie commented on YARN-4477: --- YARN-4477.003.patch fix testcase faiure:

[jira] [Commented] (YARN-4463) Container launch failure when yarn.nodemanager.log-dirs directory path contains space

[ https://issues.apache.org/jira/browse/YARN-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063822#comment-15063822 ] Sunil G commented on YARN-4463: --- Thanks for share the details. Yes, for file names "Escape Character" looks

[jira] [Created] (YARN-4481) negative pending resource of queues lead to applications in accepted status inifnitly

gu-chi created YARN-4481: Summary: negative pending resource of queues lead to applications in accepted status inifnitly Key: YARN-4481 URL: https://issues.apache.org/jira/browse/YARN-4481 Project: Hadoop

[jira] [Updated] (YARN-4481) negative pending resource of queues lead to applications in accepted status inifnitly

[ https://issues.apache.org/jira/browse/YARN-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gu-chi updated YARN-4481: - Attachment: jmx.txt > negative pending resource of queues lead to applications in accepted status > inifnitly >

[jira] [Commented] (YARN-4480) Clean up some inappropriate imports

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

[jira] [Commented] (YARN-4481) negative pending resource of queues lead to applications in accepted status inifnitly

[ https://issues.apache.org/jira/browse/YARN-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063935#comment-15063935 ] Sunil G commented on YARN-4481: --- Hi [~gu chi] Could you please help to share debug logs also. We have seen

[jira] [Updated] (YARN-4454) NM to nodelabel mapping going wrong after RM restart

[ https://issues.apache.org/jira/browse/YARN-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4454: --- Attachment: test.patch Attaching testcode to reproduce the same > NM to nodelabel mapping

[jira] [Commented] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

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

[jira] [Updated] (YARN-4467) Shell.checkIsBashSupported swallowed an interrupted exception

[ https://issues.apache.org/jira/browse/YARN-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated YARN-4467: -- Description: Edit: move this JIRA from HADOOP to YARN, as Shell.checkIsBashSupported() is used,

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064134#comment-15064134 ] MENG DING commented on YARN-4138: - Hi, [~sandflee] 1. Yes, this is the expected behavior. If you take a

[jira] [Updated] (YARN-4467) Shell.checkIsBashSupported swallowed an interrupted exception

[ https://issues.apache.org/jira/browse/YARN-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated YARN-4467: -- Description: Shell.checkIsBashSupported() creates a bash shell command to verify if the system

[jira] [Commented] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

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

[jira] [Updated] (YARN-4467) Shell.checkIsBashSupported swallowed an interrupted exception

[ https://issues.apache.org/jira/browse/YARN-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated YARN-4467: -- Description: Shell.checkIsBashSupported() creates a bash shell command to verify if the system

[jira] [Updated] (YARN-4467) Shell.checkIsBashSupported swallowed an interrupted exception

[ https://issues.apache.org/jira/browse/YARN-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated YARN-4467: -- Description: Shell.checkIsBashSupported() creates a bash shell command to verify if the system

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064004#comment-15064004 ] Sunil G commented on YARN-4304: --- Test case failures are not related. Except from known test fails, others

[jira] [Updated] (YARN-4428) Redirect RM page to AHS page when AHS turned on and RM page is not avaialable

[ https://issues.apache.org/jira/browse/YARN-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4428: --- Attachment: YARN-4428.2.2.patch .2.2 addressed the whitespace issue > Redirect RM page to AHS page when AHS

[jira] [Commented] (YARN-4234) New put APIs in TimelineClient for ats v1.5

[ https://issues.apache.org/jira/browse/YARN-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064364#comment-15064364 ] Junping Du commented on YARN-4234: -- Thanks [~xgong] for updating the patch. The latest patch LGTM in

[jira] [Commented] (YARN-4350) TestDistributedShell fails for V2 scenarios

[ https://issues.apache.org/jira/browse/YARN-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064170#comment-15064170 ] Naganarasimha G R commented on YARN-4350: - Hi [~varun_saxena], As discussed offline, this seems to

[jira] [Updated] (YARN-4290) "yarn nodes -list" should print all nodes reports information

[ https://issues.apache.org/jira/browse/YARN-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4290: -- Attachment: 0002-YARN-4290.patch Uploading a new patch as related tickets are committed Sample o/p {noformat}

[jira] [Commented] (YARN-4003) ReservationQueue inherit getAMResourceLimit() from LeafQueue, but behavior is not consistent

[ https://issues.apache.org/jira/browse/YARN-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064234#comment-15064234 ] Sunil G commented on YARN-4003: --- Hi [~curino] Thank you for the clarification. Yes, there is no cleaner

[jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

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

[jira] [Commented] (YARN-4198) CapacityScheduler locking / synchronization improvements

[ https://issues.apache.org/jira/browse/YARN-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064443#comment-15064443 ] Wangda Tan commented on YARN-4198: -- [~atumanov], Could you rebase your patch against latest trunk?

[jira] [Commented] (YARN-4428) Redirect RM page to AHS page when AHS turned on and RM page is not avaialable

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

[jira] [Commented] (YARN-4350) TestDistributedShell fails for V2 scenarios

[ https://issues.apache.org/jira/browse/YARN-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064457#comment-15064457 ] Sangjin Lee commented on YARN-4350: --- Thanks for digging deep into this [~Naganarasimha]. There might be a

[jira] [Commented] (YARN-2934) Improve handling of container's stderr

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

[jira] [Created] (YARN-4482) Default values of several config parameters are missing

Tianyin Xu created YARN-4482: Summary: Default values of several config parameters are missing Key: YARN-4482 URL: https://issues.apache.org/jira/browse/YARN-4482 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-4454) NM to nodelabel mapping going wrong after RM restart

[ https://issues.apache.org/jira/browse/YARN-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064513#comment-15064513 ] Wangda Tan commented on YARN-4454: -- [~bibinchundatt], thanks for reporting and looking at the issue. The

[jira] [Updated] (YARN-4482) Default values of several config parameters are missing

[ https://issues.apache.org/jira/browse/YARN-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tianyin Xu updated YARN-4482: - Description: In {{yarn-default.xml}}, the default values of the following parameters are commented out,

[jira] [Updated] (YARN-4482) Default values of several config parameters are missing

[ https://issues.apache.org/jira/browse/YARN-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tianyin Xu updated YARN-4482: - Description: In {{yarn-default.xml}}, the default values of the following parameters are commented out,

[jira] [Updated] (YARN-2934) Improve handling of container's stderr

[ https://issues.apache.org/jira/browse/YARN-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-2934: Attachment: YARN-2934.v2.003.patch [~jira.shegalov], Incorporating changes for ??Right now

[jira] [Commented] (YARN-4290) "yarn nodes -list" should print all nodes reports information

[ https://issues.apache.org/jira/browse/YARN-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064438#comment-15064438 ] Naganarasimha G R commented on YARN-4290: - +1 patch LGTM ! > "yarn nodes -list" should print all

[jira] [Commented] (YARN-4290) "yarn nodes -list" should print all nodes reports information

[ https://issues.apache.org/jira/browse/YARN-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064413#comment-15064413 ] Wangda Tan commented on YARN-4290: -- [~sunilg], Patch looks good to me! > "yarn nodes -list" should

[jira] [Updated] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4138: Attachment: YARN-4138.3.patch Attach latest patch that addresses [~jianhe] and [~sandflee]'s comments. I

[jira] [Commented] (YARN-4234) New put APIs in TimelineClient for ats v1.5

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

[jira] [Commented] (YARN-4224) Change the ATSv2 reader side REST interface to conform to current REST APIs' in YARN

[ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064931#comment-15064931 ] Sangjin Lee commented on YARN-4224: --- Thanks [~gtCarrera9] for the update! Then I'd like to put forward a

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065043#comment-15065043 ] Jun Gong commented on YARN-3480: Thanks for review and suggestion! {quote} regarding this logic, it is

[jira] [Commented] (YARN-4440) FSAppAttempt#getAllowedLocalityLevelByTime should init the lastScheduler time

[ https://issues.apache.org/jira/browse/YARN-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065066#comment-15065066 ] zhihai xu commented on YARN-4440: - yes, thanks [~leftnoteasy] for committing it to branch-2.8! >

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065067#comment-15065067 ] Wangda Tan commented on YARN-4392: -- Committed to branch-2.8. > ApplicationCreatedEvent event time resets

[jira] [Commented] (YARN-4424) Fix deadlock in RMAppImpl

[ https://issues.apache.org/jira/browse/YARN-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065063#comment-15065063 ] Wangda Tan commented on YARN-4424: -- Committed to branch-2.8. > Fix deadlock in RMAppImpl >

[jira] [Commented] (YARN-4422) Generic AHS sometimes doesn't show started, node, or logs on App page

[ https://issues.apache.org/jira/browse/YARN-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065065#comment-15065065 ] Wangda Tan commented on YARN-4422: -- Committed to branch-2.8. > Generic AHS sometimes doesn't show

[jira] [Commented] (YARN-4405) Support node label store in non-appendable file system

[ https://issues.apache.org/jira/browse/YARN-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065072#comment-15065072 ] Wangda Tan commented on YARN-4405: -- Committed to branch-2.8. > Support node label store in non-appendable

[jira] [Commented] (YARN-4164) Retrospect update ApplicationPriority API return type

[ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064915#comment-15064915 ] Hudson commented on YARN-4164: -- SUCCESS: Integrated in Hadoop-trunk-Commit #8999 (See

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065147#comment-15065147 ] Sunil G commented on YARN-4304: --- bq.I think the longer term fix should be, add a by-partition info to queue

[jira] [Commented] (YARN-4195) Support of node-labels in the ReservationSystem "Plan"

[ https://issues.apache.org/jira/browse/YARN-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064956#comment-15064956 ] Carlo Curino commented on YARN-4195: [~leftnoteasy], I think you are guessing right (with a wrong

[jira] [Commented] (YARN-4293) ResourceUtilization should be a part of yarn node CLI

[ https://issues.apache.org/jira/browse/YARN-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065055#comment-15065055 ] Wangda Tan commented on YARN-4293: -- Committed to branch-2.8. > ResourceUtilization should be a part of

[jira] [Commented] (YARN-4440) FSAppAttempt#getAllowedLocalityLevelByTime should init the lastScheduler time

[ https://issues.apache.org/jira/browse/YARN-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065057#comment-15065057 ] Wangda Tan commented on YARN-4440: -- Committed to branch-2.8. > FSAppAttempt#getAllowedLocalityLevelByTime

[jira] [Commented] (YARN-4418) AM Resource Limit per partition can be updated to ResourceUsage as well

[ https://issues.apache.org/jira/browse/YARN-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065058#comment-15065058 ] Wangda Tan commented on YARN-4418: -- Committed to branch-2.8. > AM Resource Limit per partition can be

[jira] [Commented] (YARN-4416) Deadlock due to synchronised get Methods in AbstractCSQueue

[ https://issues.apache.org/jira/browse/YARN-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065053#comment-15065053 ] Wangda Tan commented on YARN-4416: -- Committed to branch-2.8. > Deadlock due to synchronised get Methods

[jira] [Commented] (YARN-4225) Add preemption status to yarn queue -status for capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065054#comment-15065054 ] Wangda Tan commented on YARN-4225: -- Committed to branch-2.8. > Add preemption status to yarn queue

[jira] [Commented] (YARN-3946) Update exact reason as to why a submitted app is in ACCEPTED state to app's diagnostic message

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065060#comment-15065060 ] Wangda Tan commented on YARN-3946: -- Committed to branch-2.8. > Update exact reason as to why a submitted

[jira] [Commented] (YARN-4309) Add container launch related debug information to container logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065059#comment-15065059 ] Wangda Tan commented on YARN-4309: -- Committed to branch-2.8. > Add container launch related debug

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065078#comment-15065078 ] Wangda Tan commented on YARN-4398: -- Committed to branch-2.8. > Yarn recover functionality causes the

[jira] [Commented] (YARN-4292) ResourceUtilization should be a part of NodeInfo REST API

[ https://issues.apache.org/jira/browse/YARN-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065077#comment-15065077 ] Wangda Tan commented on YARN-4292: -- Committed to branch-2.8. > ResourceUtilization should be a part of

[jira] [Updated] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

[ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4389: -- Attachment: 0004-YARN-4389.patch Patch has gone stale. Rebasing the same. [~djp], could you please help to check

[jira] [Commented] (YARN-914) (Umbrella) Support graceful decommission of nodemanager

[ https://issues.apache.org/jira/browse/YARN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064054#comment-15064054 ] Jason Lowe commented on YARN-914: - [~danzhi] the patch should be against trunk. We always commit first

[jira] [Commented] (YARN-4480) Clean up some inappropriate imports

[ https://issues.apache.org/jira/browse/YARN-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064145#comment-15064145 ] Daniel Templeton commented on YARN-4480: Thanks, [~drankye]. Loogs good in general. Your

[jira] [Updated] (YARN-4405) Support node label store in non-appendable file system

[ https://issues.apache.org/jira/browse/YARN-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4405: -- Fix Version/s: 2.8.0 > Support node label store in non-appendable file system >

[jira] [Updated] (YARN-4480) Clean up some inappropriate imports

[ https://issues.apache.org/jira/browse/YARN-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Zheng updated YARN-4480: Attachment: YARN-4480-v2.patch Thanks Daniel. I manually edit it and uploaded a new version. > Clean up

[jira] [Commented] (YARN-914) (Umbrella) Support graceful decommission of nodemanager

[ https://issues.apache.org/jira/browse/YARN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065119#comment-15065119 ] Karthik Kambatla commented on YARN-914: --- bq. On the other hand, there are additional details and

[jira] [Created] (YARN-4484) Available Resource calculation for a queue is not correct when used with labels

Sunil G created YARN-4484: - Summary: Available Resource calculation for a queue is not correct when used with labels Key: YARN-4484 URL: https://issues.apache.org/jira/browse/YARN-4484 Project: Hadoop YARN

[jira] [Commented] (YARN-4290) "yarn nodes -list" should print all nodes reports information

[ https://issues.apache.org/jira/browse/YARN-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064783#comment-15064783 ] Wangda Tan commented on YARN-4290: -- Thanks [~Naganarasimha], [~sunilg] could you check failed tests and

[jira] [Updated] (YARN-4234) New put APIs in TimelineClient for ats v1.5

[ https://issues.apache.org/jira/browse/YARN-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4234: Attachment: YARN-4234.2015-12-18.1.patch > New put APIs in TimelineClient for ats v1.5 >

[jira] [Updated] (YARN-4234) New put APIs in TimelineClient for ats v1.5

[ https://issues.apache.org/jira/browse/YARN-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4234: Attachment: YARN-4234.2015-12-18.patch > New put APIs in TimelineClient for ats v1.5 >

[jira] [Created] (YARN-4483) HDP 2.2.9 expands the scope of AMBARI-11358.

David Tucker created YARN-4483: -- Summary: HDP 2.2.9 expands the scope of AMBARI-11358. Key: YARN-4483 URL: https://issues.apache.org/jira/browse/YARN-4483 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064874#comment-15064874 ] Wangda Tan commented on YARN-4304: -- Hi [~sunilg], 1) Changes for the max-available-to-a-queue may be

[jira] [Resolved] (YARN-4483) HDP 2.2.9 expands the scope of AMBARI-11358.

[ https://issues.apache.org/jira/browse/YARN-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan resolved YARN-4483. -- Resolution: Invalid [~dmtucker], AMBARI-11358 should handle this already, I think there's nothing needs

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064794#comment-15064794 ] Jian He commented on YARN-3480: --- thanks for updating, - regarding this logic, it is possible that a

[jira] [Commented] (YARN-4257) Move scheduler validateConf method to AbstractYarnScheduler and make it protected

[ https://issues.apache.org/jira/browse/YARN-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064886#comment-15064886 ] Wangda Tan commented on YARN-4257: -- Hi [~rhaase], Thanks for working on this patch, Patch looks good to

[jira] [Commented] (YARN-914) (Umbrella) Support graceful decommission of nodemanager

[ https://issues.apache.org/jira/browse/YARN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064737#comment-15064737 ] Daniel Zhi commented on YARN-914: - Thanks. Always commit to trunk first makes lots of sense to me. We would

[jira] [Commented] (YARN-4290) "yarn nodes -list" should print all nodes reports information

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

[jira] [Assigned] (YARN-4473) Add version information for the application and the application attempts

[ https://issues.apache.org/jira/browse/YARN-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola reassigned YARN-4473: -- Assignee: Giovanni Matteo Fumarola (was: Marco Rabozzi) > Add version

[jira] [Commented] (YARN-4234) New put APIs in TimelineClient for ats v1.5

[ https://issues.apache.org/jira/browse/YARN-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064816#comment-15064816 ] Xuan Gong commented on YARN-4234: - upload a patch to fix the checkstyle issue > New put APIs in

[jira] [Commented] (YARN-4164) Retrospect update ApplicationPriority API return type

[ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064854#comment-15064854 ] Jian He commented on YARN-4164: --- lgtm, +1 > Retrospect update ApplicationPriority API return type >

[jira] [Commented] (YARN-4238) createdTime and modifiedTime is not reported while publishing entities to ATSv2

[ https://issues.apache.org/jira/browse/YARN-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064910#comment-15064910 ] Sangjin Lee commented on YARN-4238: --- Thanks [~varun_saxena] for the summary, and [~Naganarasimha] for

[jira] [Commented] (YARN-4195) Support of node-labels in the ReservationSystem "Plan"

[ https://issues.apache.org/jira/browse/YARN-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064812#comment-15064812 ] Wangda Tan commented on YARN-4195: -- Hi [~curino], Thanks for working on this, I've took a look at your

[jira] [Updated] (YARN-4234) New put APIs in TimelineClient for ats v1.5

[ https://issues.apache.org/jira/browse/YARN-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4234: Attachment: YARN-4234.2015-11-18.patch > New put APIs in TimelineClient for ats v1.5 >

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

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

[jira] [Commented] (YARN-4164) Retrospect update ApplicationPriority API return type

[ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065162#comment-15065162 ] Rohith Sharma K S commented on YARN-4164: - Thanks [~jianhe] for review and committing patch >

[jira] [Commented] (YARN-4477) FairScheduler: encounter infinite loop in attemptScheduling

[ https://issues.apache.org/jira/browse/YARN-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065177#comment-15065177 ] Tao Jie commented on YARN-4477: --- Failed test cases are irrelevant to this patch, and work in my local

[jira] [Commented] (YARN-4481) negative pending resource of queues lead to applications in accepted status inifnitly

[ https://issues.apache.org/jira/browse/YARN-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065175#comment-15065175 ] gu-chi commented on YARN-4481: -- Same using DRC. :( Debug Log was only enabled after I saw the issue, so before

[jira] [Commented] (YARN-4481) negative pending resource of queues lead to applications in accepted status inifnitly

[ https://issues.apache.org/jira/browse/YARN-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065186#comment-15065186 ] Varun Saxena commented on YARN-4481: [~sunilg], we do not have AM debug logs. And RM debug logs are

[jira] [Commented] (YARN-4290) "yarn nodes -list" should print all nodes reports information

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

[jira] [Commented] (YARN-4480) Clean up some inappropriate imports

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

[jira] [Assigned] (YARN-4488) CapacityScheduler: Compute per-container allocation latency and roll up to get per-application and per-queue

[ https://issues.apache.org/jira/browse/YARN-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan reassigned YARN-4488: Assignee: Wangda Tan > CapacityScheduler: Compute per-container allocation latency and roll up to

[jira] [Updated] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2962: --- Hadoop Flags: Incompatible change > ZKRMStateStore: Limit the number of znodes under a znode >

[jira] [Commented] (YARN-4238) createdTime and modifiedTime is not reported while publishing entities to ATSv2

[ https://issues.apache.org/jira/browse/YARN-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065160#comment-15065160 ] Varun Saxena commented on YARN-4238: [~sjlee0], if modified time is only for debugging, is there any

[jira] [Commented] (YARN-4238) createdTime and modifiedTime is not reported while publishing entities to ATSv2

[ https://issues.apache.org/jira/browse/YARN-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065168#comment-15065168 ] Varun Saxena commented on YARN-4238: bq. If its in this way, then will it be useful for the client ?

  1   2   >