[jira] [Created] (YARN-3513) Remove unused variables in ContainersMonitorImpl

Naganarasimha G R created YARN-3513: --- Summary: Remove unused variables in ContainersMonitorImpl Key: YARN-3513 URL: https://issues.apache.org/jira/browse/YARN-3513 Project: Hadoop YARN Issu

[jira] [Commented] (YARN-3437) convert load test driver to timeline service v.2

[ https://issues.apache.org/jira/browse/YARN-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503391#comment-14503391 ] Sangjin Lee commented on YARN-3437: --- Added YARN-3512. > convert load test driver to time

[jira] [Created] (YARN-3512) add more fine-grained metrics that measure write performance

Sangjin Lee created YARN-3512: - Summary: add more fine-grained metrics that measure write performance Key: YARN-3512 URL: https://issues.apache.org/jira/browse/YARN-3512 Project: Hadoop YARN Iss

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing some MR metrics to ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503363#comment-14503363 ] Sangjin Lee commented on YARN-3046: --- Sorry my review is late for this [~djp]! Some high

[jira] [Commented] (YARN-3481) Report NM aggregated container resource utilization in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503384#comment-14503384 ] Carlo Curino commented on YARN-3481: I agree with [~vinodkv]... let's go for the new Re

[jira] [Commented] (YARN-3437) convert load test driver to timeline service v.2

[ https://issues.apache.org/jira/browse/YARN-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503383#comment-14503383 ] Sangjin Lee commented on YARN-3437: --- [~jeagles], thanks for your comment. Yes, I agree t

[jira] [Updated] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3045: Attachment: YARN-3045.20150420-1.patch WIP patch for initial review, additional test case on

[jira] [Updated] (YARN-2004) Priority scheduling support in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2004: -- Attachment: 0006-YARN-2004.patch Updated patch as per the comments. [~leftnoteasy] [~jlowe] Please check the same

[jira] [Commented] (YARN-3492) AM fails to come up because RM and NM can't connect to each other

[ https://issues.apache.org/jira/browse/YARN-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503340#comment-14503340 ] Karthik Kambatla commented on YARN-3492: I am fine with relegating it to 2.7.1 or l

[jira] [Commented] (YARN-2729) Support script based NodeLabelsProvider Interface in Distributed Node Label Configuration Setup

[ https://issues.apache.org/jira/browse/YARN-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503339#comment-14503339 ] Naganarasimha G R commented on YARN-2729: - [~wangda], any updates on this patch req

[jira] [Updated] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2003: -- Attachment: 00010-YARN-2003.patch Removing dependency with YARN-2004. > Support to process Job priority from Su

[jira] [Commented] (YARN-3481) Report NM aggregated container resource utilization in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1450#comment-1450 ] Vinod Kumar Vavilapalli commented on YARN-3481: --- We should decouple the recor

[jira] [Updated] (YARN-2740) ResourceManager side should properly handle node label modifications when distributed node label configuration enabled

[ https://issues.apache.org/jira/browse/YARN-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-2740: Attachment: YARN-2740.20150420-1.patch Hi [~wangda], i have updated the patch with the requir

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503328#comment-14503328 ] Karthik Kambatla commented on YARN-3464: [~jlowe] - do you think any of my earlier

[jira] [Updated] (YARN-3481) Report NM aggregated container resource utilization in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3481: -- Priority: Major (was: Minor) > Report NM aggregated container resource utilizati

[jira] [Updated] (YARN-3481) Report NM aggregated container resource utilization in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3481: -- Target Version/s: 2.8.0 (was: 2.7.0) 2.7.0 is done, please don't use in-progress

[jira] [Updated] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3463: -- Attachment: YARN-3463.70.patch Ok, getInfo it is, attached > Integrate OrderingPolicy Framework with Cap

[jira] [Updated] (YARN-3492) AM fails to come up because RM and NM can't connect to each other

[ https://issues.apache.org/jira/browse/YARN-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3492: -- Target Version/s: 2.7.1 (was: 2.7.0) bq. I took your mapred-site.xml and yarn-si

[jira] [Commented] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503305#comment-14503305 ] Jian He commented on YARN-3463: --- patch looks good to me. bq. as getStatusMessage suggests to

[jira] [Commented] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503302#comment-14503302 ] Wangda Tan commented on YARN-3463: -- bq. I have to say I prefer getInfo to getStatusMessage

[jira] [Created] (YARN-3511) Add errors and warnings page to ATS

Varun Vasudev created YARN-3511: --- Summary: Add errors and warnings page to ATS Key: YARN-3511 URL: https://issues.apache.org/jira/browse/YARN-3511 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-3500) Optimize ResourceManager Web loading speed

[ https://issues.apache.org/jira/browse/YARN-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503294#comment-14503294 ] Ravi Prakash commented on YARN-3500: We have gone back and forth on paging server side

[jira] [Updated] (YARN-3509) CollectorNodemanagerProtocol's authorization doesn't work

[ https://issues.apache.org/jira/browse/YARN-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3509: -- Attachment: YARN-3509.1.patch Created a patch to fix the problem > CollectorNodemanagerProtocol's author

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

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

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

[ https://issues.apache.org/jira/browse/YARN-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503265#comment-14503265 ] Jian He commented on YARN-3497: --- looks good , + 1 > ContainerManagementProtocolProxy modifie

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503258#comment-14503258 ] zhihai xu commented on YARN-3464: - Thanks [~kasha] for the detail explanation. For the sugg

[jira] [Commented] (YARN-3510) Create an extension of ProportionalCapacityPreemptionPolicy which preempts a number of containers from each application in a way which respects fairness

[ https://issues.apache.org/jira/browse/YARN-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503244#comment-14503244 ] Wangda Tan commented on YARN-3510: -- Put this as a subtask of YARN-3306 to better tracking.

[jira] [Updated] (YARN-3510) Create an extension of ProportionalCapacityPreemptionPolicy which preempts a number of containers from each application in a way which respects fairness

[ https://issues.apache.org/jira/browse/YARN-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3510: - Issue Type: Sub-task (was: Improvement) Parent: YARN-3306 > Create an extension of ProportionalCap

[jira] [Commented] (YARN-2369) Environment variable handling assumes values should be appended

[ https://issues.apache.org/jira/browse/YARN-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503230#comment-14503230 ] Dustin Cote commented on YARN-2369: --- I don't see a unit test suite dealing with env varia

[jira] [Commented] (YARN-3366) Outbound network bandwidth : classify/shape traffic originating from YARN containers

[ https://issues.apache.org/jira/browse/YARN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503181#comment-14503181 ] Sidharta Seethana commented on YARN-3366: - Thanks, [~djp] ! > Outbound network ban

[jira] [Created] (YARN-3510) Create an extension of ProportionalCapacityPreemptionPolicy which preempts a number of containers from each application in a way which respects fairness

Craig Welch created YARN-3510: - Summary: Create an extension of ProportionalCapacityPreemptionPolicy which preempts a number of containers from each application in a way which respects fairness Key: YARN-3510 URL: ht

[jira] [Updated] (YARN-3046) [Event producers] Implement MapReduce AM writing some MR metrics to ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3046: - Attachment: YARN-3046-v4.patch Upload a patch against v3 with removing changes in TimelineEvent. > [Event

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing some MR metrics to ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503175#comment-14503175 ] Junping Du commented on YARN-3046: -- bq. Shall we do nullcheck in TimelineEvent. Theoretica

[jira] [Commented] (YARN-2004) Priority scheduling support in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503158#comment-14503158 ] Sunil G commented on YARN-2004: --- Thank you very much for the comments. bq. default of defaul

[jira] [Commented] (YARN-3445) NM notify RM on running Apps in NM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503153#comment-14503153 ] Hadoop QA commented on YARN-3445: - {color:green}+1 overall{color}. Here are the results of

[jira] [Created] (YARN-3509) CollectorNodemanagerProtocol's authorization doesn't work

Zhijie Shen created YARN-3509: - Summary: CollectorNodemanagerProtocol's authorization doesn't work Key: YARN-3509 URL: https://issues.apache.org/jira/browse/YARN-3509 Project: Hadoop YARN Issue T

[jira] [Assigned] (YARN-3508) Preemption processing occuring on the main RM dispatcher

[ https://issues.apache.org/jira/browse/YARN-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reassigned YARN-3508: -- Assignee: Varun Saxena > Preemption processing occuring on the main RM dispatcher >

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing some MR metrics to ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503133#comment-14503133 ] Zhijie Shen commented on YARN-3046: --- Another issue: Shall we do nullcheck in TimelineEve

[jira] [Commented] (YARN-3366) Outbound network bandwidth : classify/shape traffic originating from YARN containers

[ https://issues.apache.org/jira/browse/YARN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503105#comment-14503105 ] Junping Du commented on YARN-3366: -- Thanks [~sidharta-s] for updating the patch! The lates

[jira] [Created] (YARN-3508) Preemption processing occuring on the main RM dispatcher

Jason Lowe created YARN-3508: Summary: Preemption processing occuring on the main RM dispatcher Key: YARN-3508 URL: https://issues.apache.org/jira/browse/YARN-3508 Project: Hadoop YARN Issue Type

[jira] [Updated] (YARN-3445) NM notify RM on running Apps in NM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3445: - Attachment: YARN-3445.patch Upload a patch. > NM notify RM on running Apps in NM-RM heartbeat > --

[jira] [Commented] (YARN-2004) Priority scheduling support in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503043#comment-14503043 ] Jason Lowe commented on YARN-2004: -- I don't think it matters if we allow negative prioriti

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

[ https://issues.apache.org/jira/browse/YARN-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503019#comment-14503019 ] Hadoop QA commented on YARN-3497: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-3503) Expose disk utilization percentage and bad disk counts on NM via JMX

[ https://issues.apache.org/jira/browse/YARN-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502951#comment-14502951 ] Hadoop QA commented on YARN-3503: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

[ https://issues.apache.org/jira/browse/YARN-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3497: - Attachment: YARN-3497.002.patch Thanks for the review, Jian! I updated the patch to use this.conf when set

[jira] [Updated] (YARN-3503) Expose disk utilization percentage and bad disk counts on NM via JMX

[ https://issues.apache.org/jira/browse/YARN-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3503: Description: It would be useful to expose the disk utilization as well as the number of bad local dis

[jira] [Updated] (YARN-3503) Expose disk utilization percentage and bad disk counts on NM via JMX

[ https://issues.apache.org/jira/browse/YARN-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3503: Attachment: YARN-3503.0.patch First cut of the patch. Currently exposes the information only via JMX.

[jira] [Commented] (YARN-3502) Expose number of unhealthy disks on NM via JMX

[ https://issues.apache.org/jira/browse/YARN-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502888#comment-14502888 ] Varun Vasudev commented on YARN-3502: - There is a lot of common work between this and Y

[jira] [Updated] (YARN-3503) Expose disk utilization percentage and bad disk counts on NM via JMX

[ https://issues.apache.org/jira/browse/YARN-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3503: Summary: Expose disk utilization percentage and bad disk counts on NM via JMX (was: Expose disk util

[jira] [Resolved] (YARN-3502) Expose number of unhealthy disks on NM via JMX

[ https://issues.apache.org/jira/browse/YARN-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev resolved YARN-3502. - Resolution: Won't Fix > Expose number of unhealthy disks on NM via JMX > --

[jira] [Commented] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502813#comment-14502813 ] Wilfred Spiegelenburg commented on YARN-3491: - Could this change not cause a ne

[jira] [Commented] (YARN-3177) Fix the order of the parameters in YarnConfiguration

[ https://issues.apache.org/jira/browse/YARN-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502750#comment-14502750 ] Brahma Reddy Battula commented on YARN-3177: Agreed with chris..Hence closing t

[jira] [Commented] (YARN-3177) Fix the order of the parameters in YarnConfiguration

[ https://issues.apache.org/jira/browse/YARN-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502746#comment-14502746 ] Brahma Reddy Battula commented on YARN-3177: Closing this issue.. > Fix the or

[jira] [Resolved] (YARN-3177) Fix the order of the parameters in YarnConfiguration

[ https://issues.apache.org/jira/browse/YARN-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved YARN-3177. Resolution: Not A Problem > Fix the order of the parameters in YarnConfiguration > --

[jira] [Commented] (YARN-3494) Expose AM resource limit and user limit in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502713#comment-14502713 ] Hadoop QA commented on YARN-3494: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3494) Expose AM resource limit and user limit in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502707#comment-14502707 ] Rohith commented on YARN-3494: -- One self review is move below code to setupQueueConfigs. Will

[jira] [Commented] (YARN-3494) Expose AM resource limit and user limit in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502635#comment-14502635 ] Rohith commented on YARN-3494: -- Updated the patch adding metric for AMResourceLimit, UserAMRes

[jira] [Updated] (YARN-3494) Expose AM resource limit and user limit in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3494: - Attachment: 0001-YARN-3494.patch > Expose AM resource limit and user limit in QueueMetrics > -

<    1   2