[jira] [Commented] (YARN-3547) FairScheduler: Apps that have no resource demand should not participate scheduling

[ https://issues.apache.org/jira/browse/YARN-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544995#comment-14544995 ] Xianyin Xin commented on YARN-3547: --- [~kasha], can you please have a look? > FairSchedul

[jira] [Updated] (YARN-3547) FairScheduler: Apps that have no resource demand should not participate scheduling

[ https://issues.apache.org/jira/browse/YARN-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-3547: -- Attachment: YARN-3547.005.patch A patch using {{getDemand() - getResourceUsage()}}. > FairScheduler: App

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544988#comment-14544988 ] Rohith commented on YARN-3646: -- Setting RetryPolicies.RETRY_FOREVER for exceptionToPolicyMap a

[jira] [Commented] (YARN-3644) Node manager shuts down if unable to connect with RM

[ https://issues.apache.org/jira/browse/YARN-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544971#comment-14544971 ] Srikanth Sundarrajan commented on YARN-3644: {quote} Setting the yarn.resourcem

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544959#comment-14544959 ] Rohith commented on YARN-3646: -- I was copied *yarn.resourcemanager.connect.wait-ms* from descr

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544947#comment-14544947 ] Rohith commented on YARN-3646: -- RetryPolicies.RETRY_FOREVER should also should use exceptionTo

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544938#comment-14544938 ] Rohith commented on YARN-3646: -- Thanks for the explanation.. I got the problem in my machines

[jira] [Commented] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544920#comment-14544920 ] Rohith commented on YARN-3642: -- How many nodemanagers are running? If it more than 1 then I am

[jira] [Created] (YARN-3650) Consider concurrency situations for TimelineWriter

Vrushali C created YARN-3650: Summary: Consider concurrency situations for TimelineWriter Key: YARN-3650 URL: https://issues.apache.org/jira/browse/YARN-3650 Project: Hadoop YARN Issue Type: Sub-

[jira] [Commented] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544909#comment-14544909 ] Akira AJISAKA commented on YARN-2336: - The findbugs warning looks unrelated to the patc

[jira] [Created] (YARN-3649) Allow configurable prefix for hbase table names (like prod, exp, test etc)

Vrushali C created YARN-3649: Summary: Allow configurable prefix for hbase table names (like prod, exp, test etc) Key: YARN-3649 URL: https://issues.apache.org/jira/browse/YARN-3649 Project: Hadoop YARN

[jira] [Commented] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

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

[jira] [Updated] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

[ https://issues.apache.org/jira/browse/YARN-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3583: -- Attachment: 0002-YARN-3583.patch Thank you [~leftnoteasy] for sharing the comments. Please find updated patch ad

[jira] [Commented] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

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

[jira] [Commented] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

[ https://issues.apache.org/jira/browse/YARN-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544851#comment-14544851 ] Craig Welch commented on YARN-3632: --- Now with testing > Ordering policy should be allowe

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

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

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544815#comment-14544815 ] Raju Bairishetti commented on YARN-3646: Thanks for the quick response. I have rep

[jira] [Updated] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

[ https://issues.apache.org/jira/browse/YARN-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3632: -- Attachment: YARN-3632.3.patch > Ordering policy should be allowed to reorder an application when demand

[jira] [Commented] (YARN-3526) ApplicationMaster tracking URL is incorrectly redirected on a QJM cluster

[ https://issues.apache.org/jira/browse/YARN-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544803#comment-14544803 ] Weiwei Yang commented on YARN-3526: --- Any more suggestion to the patch ? I think it is rea

[jira] [Updated] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-2336: Attachment: YARN-2336.008.patch v8 patch: Fixed checkstyle and whitespace issues. > Fair scheduler R

[jira] [Updated] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[ https://issues.apache.org/jira/browse/YARN-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3505: Hadoop Flags: (was: Reviewed) > Node's Log Aggregation Report with SUCCEED should not cached in RMApps > --

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[ https://issues.apache.org/jira/browse/YARN-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544771#comment-14544771 ] Xuan Gong commented on YARN-3505: - reopen the ticket and attached an addendum patch... {co

[jira] [Reopened] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[ https://issues.apache.org/jira/browse/YARN-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reopened YARN-3505: - > Node's Log Aggregation Report with SUCCEED should not cached in RMApps >

[jira] [Updated] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[ https://issues.apache.org/jira/browse/YARN-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3505: Attachment: YARN-3505.addendum.patch > Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[jira] [Commented] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

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

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544756#comment-14544756 ] Vrushali C commented on YARN-3411: -- Thanks [~sjlee0] and [~jrottinghuis] for the feedback

[jira] [Updated] (YARN-3565) NodeHeartbeatRequest/RegisterNodeManagerRequest should use NodeLabel object instead of String

[ https://issues.apache.org/jira/browse/YARN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3565: Attachment: YARN-3565.20150515-1.patch > NodeHeartbeatRequest/RegisterNodeManagerRequest shou

[jira] [Updated] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

[ https://issues.apache.org/jira/browse/YARN-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3632: -- Attachment: YARN-3632.1.patch > Ordering policy should be allowed to reorder an application when demand

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544708#comment-14544708 ] zhihai xu commented on YARN-3591: - I think the current code call {{removeResource}} instead

[jira] [Commented] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

[ https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544703#comment-14544703 ] Karthik Kambatla commented on YARN-3635: With FairScheduler, if this patch is appli

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544692#comment-14544692 ] Joep Rottinghuis commented on YARN-3411: Ok, admitted that I have not yet read Sang

[jira] [Commented] (YARN-3645) ResourceManager can't start success if attribute value of "aclSubmitApps" is null in fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544674#comment-14544674 ] Gabor Liptak commented on YARN-3645: Would this configuration file with empty node cons

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544659#comment-14544659 ] Sangjin Lee commented on YARN-3411: --- The latest patch looks pretty good. I think we're al

[jira] [Commented] (YARN-3388) Allocation in LeafQueue could get stuck because DRF calculator isn't well supported when computing user-limit

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

[jira] [Commented] (YARN-3244) Add user specified information for clean-up container in ApplicationSubmissionContext

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

[jira] [Commented] (YARN-3625) RollingLevelDBTimelineStore Incorrectly Forbids Related Entity in Same Put

[ https://issues.apache.org/jira/browse/YARN-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544617#comment-14544617 ] Zhijie Shen commented on YARN-3625: --- Check relationship between the entities in one put r

[jira] [Commented] (YARN-1519) check if sysconf is implemented before using it

[ https://issues.apache.org/jira/browse/YARN-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544616#comment-14544616 ] Hudson commented on YARN-1519: -- FAILURE: Integrated in Hadoop-trunk-Commit #7835 (See [https:

[jira] [Updated] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

[ https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3635: - Attachment: YARN-3635.3.patch Thanks [~jianhe]'s review. Uploaded ver.3 patch with modified name. And forg

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

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

[jira] [Commented] (YARN-3388) Allocation in LeafQueue could get stuck because DRF calculator isn't well supported when computing user-limit

[ https://issues.apache.org/jira/browse/YARN-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544602#comment-14544602 ] Wangda Tan commented on YARN-3388: -- Thanks updating [~nroberts], took at look at latest pa

[jira] [Commented] (YARN-3624) ApplicationHistoryServer reverses the order of the filters it gets

[ https://issues.apache.org/jira/browse/YARN-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544574#comment-14544574 ] Jonathan Eagles commented on YARN-3624: --- Perhaps we can add some documentation about

[jira] [Commented] (YARN-3624) ApplicationHistoryServer reverses the order of the filters it gets

[ https://issues.apache.org/jira/browse/YARN-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544554#comment-14544554 ] Zhijie Shen commented on YARN-3624: --- I think it should be fine overall. One difference I

[jira] [Updated] (YARN-1519) check if sysconf is implemented before using it

[ https://issues.apache.org/jira/browse/YARN-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-1519: --- Fix Version/s: 2.8.0 > check if sysconf is implemented before using it > --

[jira] [Commented] (YARN-1519) check if sysconf is implemented before using it

[ https://issues.apache.org/jira/browse/YARN-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544532#comment-14544532 ] Ravi Prakash commented on YARN-1519: Thanks for the patch Eric and Radim. +1. lgtm. Wil

[jira] [Commented] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

[ https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544533#comment-14544533 ] Jian He commented on YARN-3635: --- looks good overall, getQueueNameOfNewApp, may be call it get

[jira] [Commented] (YARN-1621) Add CLI to list rows of

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

[jira] [Updated] (YARN-3244) Add user specified information for clean-up container in ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3244: Attachment: YARN-3244.3.patch Address all the comments > Add user specified information for clean-up contain

[jira] [Commented] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544502#comment-14544502 ] Lee Hounshell commented on YARN-3642: - Yes, we have a proper /etc/hosts That is not the

[jira] [Assigned] (YARN-3648) ContainerExecutor interface methods are too brittle

[ https://issues.apache.org/jira/browse/YARN-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana reassigned YARN-3648: --- Assignee: Sidharta Seethana > ContainerExecutor interface methods are too brittle > --

[jira] [Commented] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544462#comment-14544462 ] Lee Hounshell commented on YARN-3642: - Here is a copy of our yarn-site.xml:

[jira] [Updated] (YARN-3388) Allocation in LeafQueue could get stuck because DRF calculator isn't well supported when computing user-limit

[ https://issues.apache.org/jira/browse/YARN-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Roberts updated YARN-3388: - Attachment: YARN-3388-v2.patch [~leftnoteasy], please take a look at this version of the patch. >

[jira] [Commented] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544459#comment-14544459 ] Lee Hounshell commented on YARN-3642: - Here is a copy of our common /etc/hosts: ::1

[jira] [Commented] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

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

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544404#comment-14544404 ] Eric Payne commented on YARN-2069: -- Hi [~mayank_bansal]. Thanks for working through the de

[jira] [Commented] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

[ https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544390#comment-14544390 ] Chang Li commented on YARN-2421: Thanks [~jlowe] for valuable feedback! have updated my pat

[jira] [Commented] (YARN-2556) Tool to measure the performance of the timeline server

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

[jira] [Commented] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544450#comment-14544450 ] Lee Hounshell commented on YARN-3642: - Yes, we have the same /etc/hosts on all machines

[jira] [Created] (YARN-3648) ContainerExecutor interface methods are too brittle

Sidharta Seethana created YARN-3648: --- Summary: ContainerExecutor interface methods are too brittle Key: YARN-3648 URL: https://issues.apache.org/jira/browse/YARN-3648 Project: Hadoop YARN I

[jira] [Commented] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544334#comment-14544334 ] Sangjin Lee commented on YARN-2556: --- Thanks for the latest patch [~lichangleo]! You migh

[jira] [Updated] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3411: - Attachment: YARN-3411-YARN-2928.002.patch Attaching patch YARN-3411-YARN-2928.002.patch with the fixes for

[jira] [Resolved] (YARN-2829) After restart, RM should create running-attempt before AM register

[ https://issues.apache.org/jira/browse/YARN-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-2829. --- Resolution: Not A Problem > After restart, RM should create running-attempt before AM register > --

[jira] [Commented] (YARN-2829) After restart, RM should create running-attempt before AM register

[ https://issues.apache.org/jira/browse/YARN-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544317#comment-14544317 ] Jian He commented on YARN-2829: --- I think it's now already the case that attempts are added in

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-2556: --- Attachment: YARN-2556.8.patch > Tool to measure the performance of the timeline server > --

[jira] [Updated] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

[ https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-2421: --- Attachment: YARN-2421.9.patch > CapacityScheduler still allocates containers to an app in the FINISHING state >

[jira] [Updated] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

[ https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-2421: --- Attachment: YARN-2421.8.patch > CapacityScheduler still allocates containers to an app in the FINISHING state >

[jira] [Commented] (YARN-3630) YARN should suggest a heartbeat interval for applications

[ https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544244#comment-14544244 ] Karthik Kambatla commented on YARN-3630: Number of events in the dispatcher is defi

[jira] [Commented] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

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

[jira] [Commented] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and NN go down at the same time.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544235#comment-14544235 ] Allen Wittenauer commented on YARN-3639: OK, just making sure there wasn't some wei

[jira] [Commented] (YARN-3609) Move load labels from storage from serviceInit to serviceStart to make it works with RM HA case.

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

[jira] [Updated] (YARN-1621) Add CLI to list rows of

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Ługowski updated YARN-1621: --- Attachment: YARN-1621.6.patch > Add CLI to list rows of state of container> >

[jira] [Updated] (YARN-1621) Add CLI to list rows of

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Ługowski updated YARN-1621: --- Attachment: (was: YARN-1621.6.patch) > Add CLI to list rows of state of container> > -

[jira] [Commented] (YARN-3624) ApplicationHistoryServer reverses the order of the filters it gets

[ https://issues.apache.org/jira/browse/YARN-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544194#comment-14544194 ] Jonathan Eagles commented on YARN-3624: --- Patch looks fine assuming this change won't

[jira] [Commented] (YARN-3624) ApplicationHistoryServer reverses the order of the filters it gets

[ https://issues.apache.org/jira/browse/YARN-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544192#comment-14544192 ] Jonathan Eagles commented on YARN-3624: --- This change solves this issue where users ha

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544190#comment-14544190 ] Sangjin Lee commented on YARN-3411: --- Vrushali and I spoke offline on the findbugs issues

[jira] [Commented] (YARN-3624) ApplicationHistoryServer reverses the order of the filters it gets

[ https://issues.apache.org/jira/browse/YARN-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544185#comment-14544185 ] Mit Desai commented on YARN-3624: - [~jeagles] can you take a look on this? > ApplicationHi

[jira] [Updated] (YARN-3647) RMWebServices api's should use updated api from CommonNodeLabelsManager to get NodeLabel object

[ https://issues.apache.org/jira/browse/YARN-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3647: -- Attachment: 0001-YARN-3647.patch Attaching an initial version of patch. getLabelsOnNode api also changed to use

[jira] [Updated] (YARN-3647) RMWebServices api's should use updated api from CommonNodeLabelsManager to get NodeLabel object

[ https://issues.apache.org/jira/browse/YARN-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3647: - Issue Type: Sub-task (was: Bug) Parent: YARN-2492 > RMWebServices api's should use updated api fro

[jira] [Created] (YARN-3647) RMWebServices api's should use updated api from CommonNodeLabelsManager to get NodeLabel object

Sunil G created YARN-3647: - Summary: RMWebServices api's should use updated api from CommonNodeLabelsManager to get NodeLabel object Key: YARN-3647 URL: https://issues.apache.org/jira/browse/YARN-3647 Project

[jira] [Commented] (YARN-3630) YARN should suggest a heartbeat interval for applications

[ https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544157#comment-14544157 ] Wangda Tan commented on YARN-3630: -- [~xinxianyin], Thanks for sharing your thoughts, I thi

[jira] [Commented] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

[ https://issues.apache.org/jira/browse/YARN-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544142#comment-14544142 ] Wangda Tan commented on YARN-3583: -- 1. NodeIdToLabelsProto can be removed? 2. NodeIdToLabe

[jira] [Commented] (YARN-2429) LCE should blacklist based upon group

[ https://issues.apache.org/jira/browse/YARN-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544140#comment-14544140 ] Allen Wittenauer commented on YARN-2429: Changing the label to newbie, since this i

[jira] [Updated] (YARN-2429) LCE should blacklist based upon group

[ https://issues.apache.org/jira/browse/YARN-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-2429: --- Labels: newbie (was: ) > LCE should blacklist based upon group > -

[jira] [Commented] (YARN-2429) LCE should blacklist based upon group

[ https://issues.apache.org/jira/browse/YARN-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544139#comment-14544139 ] Allen Wittenauer commented on YARN-2429: bq. Unless I'm mistaken, the blacklisting

[jira] [Updated] (YARN-2429) LCE should blacklist based upon group

[ https://issues.apache.org/jira/browse/YARN-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-2429: --- Component/s: security > LCE should blacklist based upon group > ---

[jira] [Commented] (YARN-2942) Aggregated Log Files should be combined

[ https://issues.apache.org/jira/browse/YARN-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544109#comment-14544109 ] Robert Kanter commented on YARN-2942: - The log delays in aggregation should be fine if

[jira] [Updated] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[ https://issues.apache.org/jira/browse/YARN-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3505: - Target Version/s: 2.8.0, 2.7.1 (was: 2.7.1) Forget to mention, given the previous patch YARN-1402 is in 2.

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

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

[jira] [Commented] (YARN-2748) Upload logs in the sub-folders under the local log dir when aggregating logs

[ https://issues.apache.org/jira/browse/YARN-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544093#comment-14544093 ] Vinod Kumar Vavilapalli commented on YARN-2748: --- bq. One question is if we wa

[jira] [Updated] (YARN-3609) Move load labels from storage from serviceInit to serviceStart to make it works with RM HA case.

[ https://issues.apache.org/jira/browse/YARN-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3609: - Attachment: YARN-3609.2.patch Attached ver.2 patch, contains tests. > Move load labels from storage from s

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

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

[jira] [Commented] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

[ https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544037#comment-14544037 ] Wangda Tan commented on YARN-3635: -- Failed test is not related to this change, which is tr

[jira] [Reopened] (YARN-3617) Fix unused variable to get CPU frequency on Windows systems

[ https://issues.apache.org/jira/browse/YARN-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K reopened YARN-3617: - This issue doesn't seem to be fixed/committed, reopening it. [~xafero], Please note that committers will revi

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543929#comment-14543929 ] Devaraj K commented on YARN-41: --- || NM Graceful Shutdown||NM Recovery Enabled\\yarn.nodemanage

[jira] [Commented] (YARN-2921) Fix MockRM/MockAM#waitForState sleep too long

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543890#comment-14543890 ] Hudson commented on YARN-2921: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2143 (See [htt

[jira] [Commented] (YARN-3537) NPE when NodeManager.serviceInit fails and stopRecoveryStore invoked

[ https://issues.apache.org/jira/browse/YARN-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543893#comment-14543893 ] Hudson commented on YARN-3537: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2143 (See [htt

[jira] [Updated] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

[ https://issues.apache.org/jira/browse/YARN-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3583: -- Description: Similar to YARN-3521, use NodeLabel objects in YarnClient side apis. getLabelsToNodes/getNodeToLabel

[jira] [Commented] (YARN-1612) FairScheduler: Enable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543914#comment-14543914 ] Chen He commented on YARN-1612: --- Thank you for the review, [~kasha], I did change FairSchedu

[jira] [Updated] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

[ https://issues.apache.org/jira/browse/YARN-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3583: -- Attachment: 0001-YARN-3583.patch Uploading an initial version patch. This path covers changes in YarnClient/Resou

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543904#comment-14543904 ] Hudson commented on YARN-3626: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2143 (See [htt

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543903#comment-14543903 ] Hudson commented on YARN-3641: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2143 (See [htt

  1   2   >