[jira] [Commented] (YARN-3416) deadlock in a job between map and reduce cores allocation

[ https://issues.apache.org/jira/browse/YARN-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386258#comment-14386258 ] mai shurong commented on YARN-3416: --- The job ran two days ago, now the AM logs is

[jira] [Updated] (YARN-2123) Progress bars in Web UI always at 100% due to non-US locale

[ https://issues.apache.org/jira/browse/YARN-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-2123: Attachment: YARN-2123-002.patch Rebased. Progress bars in Web UI always at 100% due to non-US

[jira] [Commented] (YARN-3416) deadlock in a job between map and reduce cores allocation

[ https://issues.apache.org/jira/browse/YARN-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386301#comment-14386301 ] mai shurong commented on YARN-3416: --- The AM logs are repeately printed such as follows:

[jira] [Commented] (YARN-3416) deadlock in a job between map and reduce cores allocation

[ https://issues.apache.org/jira/browse/YARN-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386300#comment-14386300 ] mai shurong commented on YARN-3416: --- The AM logs are repeately printed such as follows:

[jira] [Commented] (YARN-3416) deadlock in a job between map and reduce cores allocation

[ https://issues.apache.org/jira/browse/YARN-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386244#comment-14386244 ] mai shurong commented on YARN-3416: --- In YARN-1680,there are only 4 NodeManagers in

[jira] [Commented] (YARN-2123) Progress bars in Web UI always at 100% due to non-US locale

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

[jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386576#comment-14386576 ] Varun Saxena commented on YARN-3047: [~sjlee0], the initial scope of this JIRA as you

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386584#comment-14386584 ] Varun Saxena commented on YARN-3051: bq. given a time window, query all entities in

[jira] [Updated] (YARN-3293) Track and display capacity scheduler health metrics in web UI

[ https://issues.apache.org/jira/browse/YARN-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3293: Attachment: apache-yarn-3293.1.patch Updated patch to address findbugs warnings. Track and display

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-v8.patch There are still two issues with v7 version: 1. cpuTimeMs in

[jira] [Created] (YARN-3419) ConcurrentModificationException in FSLeafQueue

Dustin Cote created YARN-3419: - Summary: ConcurrentModificationException in FSLeafQueue Key: YARN-3419 URL: https://issues.apache.org/jira/browse/YARN-3419 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-3293) Track and display capacity scheduler health metrics in web UI

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

[jira] [Created] (YARN-3418) AM to be able to set/update web URL and IPC ports post-registration

Steve Loughran created YARN-3418: Summary: AM to be able to set/update web URL and IPC ports post-registration Key: YARN-3418 URL: https://issues.apache.org/jira/browse/YARN-3418 Project: Hadoop YARN

[jira] [Commented] (YARN-896) Roll up for long-lived services in YARN

[ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386537#comment-14386537 ] Steve Loughran commented on YARN-896: - Link to YARN-3418: AM to be able to update web

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386581#comment-14386581 ] Varun Saxena commented on YARN-3051: bq. Currently we're not including our first-class

[jira] [Updated] (YARN-3293) Track and display capacity scheduler health metrics in web UI

[ https://issues.apache.org/jira/browse/YARN-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3293: Attachment: Screen Shot 2015-03-30 at 4.30.14 PM.png Attached screenshot of additions to the

[jira] [Updated] (YARN-3293) Track and display capacity scheduler health metrics in web UI

[ https://issues.apache.org/jira/browse/YARN-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3293: Attachment: apache-yarn-3293.0.patch Uploaded initial patch Track and display capacity scheduler

[jira] [Created] (YARN-3417) AM to be able to exit with a request saying restart me with these (possibly updated) resource requirements)

Steve Loughran created YARN-3417: Summary: AM to be able to exit with a request saying restart me with these (possibly updated) resource requirements) Key: YARN-3417 URL:

[jira] [Commented] (YARN-896) Roll up for long-lived services in YARN

[ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386530#comment-14386530 ] Steve Loughran commented on YARN-896: - YARN-3417: AM to be able to exit with a request

[jira] [Assigned] (YARN-3418) AM to be able to set/update web URL and IPC ports post-registration

[ https://issues.apache.org/jira/browse/YARN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-3418: Assignee: Rohith AM to be able to set/update web URL and IPC ports post-registration

[jira] [Commented] (YARN-3293) Track and display capacity scheduler health metrics in web UI

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

[jira] [Commented] (YARN-3419) ConcurrentModificationException in FSLeafQueue

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

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

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

[jira] [Commented] (YARN-3419) ConcurrentModificationException in FSLeafQueue

[ https://issues.apache.org/jira/browse/YARN-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386825#comment-14386825 ] Tsuyoshi Ozawa commented on YARN-3419: -- [~cotedm], Thank you for reporting. I think

[jira] [Assigned] (YARN-3417) AM to be able to exit with a request saying restart me with these (possibly updated) resource requirements)

[ https://issues.apache.org/jira/browse/YARN-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reassigned YARN-3417: -- Assignee: Varun Saxena AM to be able to exit with a request saying restart me with these

[jira] [Updated] (YARN-3293) Track and display capacity scheduler health metrics in web UI

[ https://issues.apache.org/jira/browse/YARN-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3293: Attachment: apache-yarn-3293.2.patch Uploaded patch to fix failing web service tests, Track and

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386847#comment-14386847 ] Junping Du commented on YARN-3304: -- Hi [~adhoot], [~kasha] and [~vinodkv], I am sure v8

[jira] [Commented] (YARN-3169) drop the useless yarn overview document

[ https://issues.apache.org/jira/browse/YARN-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386861#comment-14386861 ] Tsuyoshi Ozawa commented on YARN-3169: -- [~brahmareddy] the link to overview document

[jira] [Updated] (YARN-3419) ConcurrentModificationException in FSLeafQueue

[ https://issues.apache.org/jira/browse/YARN-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Cote updated YARN-3419: -- Attachment: YARN-3419-1.patch Attaching a patch moving to a thread safe ArrayList implementation

[jira] [Commented] (YARN-3419) ConcurrentModificationException in FSLeafQueue

[ https://issues.apache.org/jira/browse/YARN-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386850#comment-14386850 ] Dustin Cote commented on YARN-3419: --- [~ozawa] yep that will probably fix it, just on the

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

[ https://issues.apache.org/jira/browse/YARN-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386960#comment-14386960 ] Jian Fang commented on YARN-2923: - Thanks Naganarasimha for your quick update. I think

[jira] [Commented] (YARN-3293) Track and display capacity scheduler health metrics in web UI

[ https://issues.apache.org/jira/browse/YARN-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386975#comment-14386975 ] Varun Vasudev commented on YARN-3293: - The test failures are unrelated. The findbugs

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387062#comment-14387062 ] Sangjin Lee commented on YARN-3051: --- {quote} I agree we need to support all these

[jira] [Updated] (YARN-3422) relatedentities always return empty list when primary filter is set

[ https://issues.apache.org/jira/browse/YARN-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3422: --- Attachment: YARN-3422.1.patch relatedentities always return empty list when primary filter is set

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

[ https://issues.apache.org/jira/browse/YARN-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387023#comment-14387023 ] Naganarasimha G R commented on YARN-2923: - Thanks [~john.jian.fang] for your

[jira] [Updated] (YARN-3420) Typos in SwiftNativeFileSystem and SwiftNativeFileSystemStore Javadoc

[ https://issues.apache.org/jira/browse/YARN-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3420: --- Component/s: (was: documentation) Typos in SwiftNativeFileSystem and

[jira] [Created] (YARN-3421) Typos in SwiftNativeFileSystem and SwiftNativeFileSystemStore Javadoc

Chen He created YARN-3421: - Summary: Typos in SwiftNativeFileSystem and SwiftNativeFileSystemStore Javadoc Key: YARN-3421 URL: https://issues.apache.org/jira/browse/YARN-3421 Project: Hadoop YARN

[jira] [Updated] (YARN-3420) Typos in SwiftNativeFileSystem and SwiftNativeFileSystemStore Javadoc

[ https://issues.apache.org/jira/browse/YARN-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3420: --- Component/s: documentation Typos in SwiftNativeFileSystem and

[jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387112#comment-14387112 ] Naganarasimha G R commented on YARN-3044: - Hi [~zjshen], [~djp] [~sjlee0], I am

[jira] [Created] (YARN-3420) Typos in SwiftNativeFileSystem and SwiftNativeFileSystemStore Javadoc

Chen He created YARN-3420: - Summary: Typos in SwiftNativeFileSystem and SwiftNativeFileSystemStore Javadoc Key: YARN-3420 URL: https://issues.apache.org/jira/browse/YARN-3420 Project: Hadoop YARN

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387021#comment-14387021 ] Hudson commented on YARN-3304: -- FAILURE: Integrated in Hadoop-trunk-Commit #7461 (See

[jira] [Updated] (YARN-3417) AM to be able to exit with a request saying restart me with these (possibly updated) resource requirements

[ https://issues.apache.org/jira/browse/YARN-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-3417: Summary: AM to be able to exit with a request saying restart me with these (possibly updated) resource

[jira] [Updated] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3361: - Attachment: YARN-3361.1.patch Attached ver.1 patch for review. CapacityScheduler side changes to support

[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: 0005-YARN-2003.patch Uploading a patch as per the comments. [~leftnoteasy] kindly check. Support

[jira] [Commented] (YARN-3293) Track and display capacity scheduler health metrics in web UI

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

[jira] [Commented] (YARN-3422) relatedentities always return empty list when primary filter is set

[ https://issues.apache.org/jira/browse/YARN-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387109#comment-14387109 ] Chang Li commented on YARN-3422: Hi [~zjshen], could you help me verify if this is a right

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386997#comment-14386997 ] Vinod Kumar Vavilapalli commented on YARN-3304: --- Tx for the update, [~djp].

[jira] [Commented] (YARN-3416) deadlock in a job between map and reduce cores allocation

[ https://issues.apache.org/jira/browse/YARN-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386992#comment-14386992 ] Ray Chiang commented on YARN-3416: -- There probably is a bug here, but what value do you

[jira] [Commented] (YARN-2423) TimelineClient should wrap all GET APIs to facilitate Java users

[ https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386996#comment-14386996 ] Steve Loughran commented on YARN-2423: -- Note that I've implemented the production-side

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

[ https://issues.apache.org/jira/browse/YARN-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387065#comment-14387065 ] Jian Fang commented on YARN-2923: - That would require that our controller to monitor the

[jira] [Created] (YARN-3422) relatedentities always return empty list when primary filter is set

Chang Li created YARN-3422: -- Summary: relatedentities always return empty list when primary filter is set Key: YARN-3422 URL: https://issues.apache.org/jira/browse/YARN-3422 Project: Hadoop YARN

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14387091#comment-14387091 ] Arun Suresh commented on YARN-2962: --- [~varun_saxena], Thanks for the patch. It looks

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387114#comment-14387114 ] Sunil G commented on YARN-3136: --- Hi [~jlowe] [~jianhe] {noformat} Bug type

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387136#comment-14387136 ] Sangjin Lee commented on YARN-3051: --- cc [~vrushalic] As for whether readers should

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387172#comment-14387172 ] Vrushali C commented on YARN-3051: -- That sounds correct, Sangjin. I will add that to the

[jira] [Commented] (YARN-3422) relatedentities always return empty list when primary filter is set

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

[jira] [Commented] (YARN-2495) Allow admin specify labels from each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387240#comment-14387240 ] Hudson commented on YARN-2495: -- FAILURE: Integrated in Hadoop-trunk-Commit #7467 (See

[jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests

[ https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387310#comment-14387310 ] Jian Fang commented on YARN-796: I took a look at

[jira] [Updated] (YARN-3420) Typos in SwiftNativeFileSystem and SwiftNativeFileSystemStore Javadoc

[ https://issues.apache.org/jira/browse/YARN-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-3420: -- Assignee: (was: Chen He) Typos in SwiftNativeFileSystem and SwiftNativeFileSystemStore Javadoc

[jira] [Commented] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

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

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387351#comment-14387351 ] Zhijie Shen commented on YARN-3051: --- bq. Wanted to know, how will app context information

[jira] [Commented] (YARN-2901) Add errors and warning stats to RM, NM web UI

[ https://issues.apache.org/jira/browse/YARN-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387203#comment-14387203 ] Wangda Tan commented on YARN-2901: -- Hi Varun, Thanks for updating patch, I took a look

[jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387153#comment-14387153 ] Sangjin Lee commented on YARN-3047: --- I am fine with committing this patch with the

[jira] [Commented] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

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

[jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387175#comment-14387175 ] Sangjin Lee commented on YARN-3044: --- bq. I am planning to go ahead with the approach

[jira] [Updated] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3361: - Attachment: YARN-3361.2.patch Attached ver.2 patch fixed findbugs warnings, failed tests are not related

[jira] [Resolved] (YARN-3420) Typos in SwiftNativeFileSystem and SwiftNativeFileSystemStore Javadoc

[ https://issues.apache.org/jira/browse/YARN-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He resolved YARN-3420. --- Resolution: Duplicate Release Note: Duplicated of HADOOP-11775 Typos in SwiftNativeFileSystem and

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387345#comment-14387345 ] Hitesh Shah commented on YARN-3304: --- Sigh. This broke compatibility again. Was there a

[jira] [Commented] (YARN-3415) Non-AM containers can be counted towards amResourceUsage of a fairscheduler queue

[ https://issues.apache.org/jira/browse/YARN-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387425#comment-14387425 ] Sandy Ryza commented on YARN-3415: -- This looks mostly reasonable. A few comments: * In

[jira] [Commented] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387491#comment-14387491 ] Vrushali C commented on YARN-3391: -- bq. I propose: flow name: String:

[jira] [Commented] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387523#comment-14387523 ] Zhijie Shen commented on YARN-3334: --- [~djp], [~sjlee0], [~gtCarrera9], per may previous

[jira] [Comment Edited] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387523#comment-14387523 ] Zhijie Shen edited comment on YARN-3334 at 3/30/15 10:37 PM: -

[jira] [Commented] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387552#comment-14387552 ] Li Lu commented on YARN-3334: - OK, that solution LGTM. I'd like to double check if there are

[jira] [Commented] (YARN-3388) userlimit isn't playing well with DRF calculator

[ https://issues.apache.org/jira/browse/YARN-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387413#comment-14387413 ] Wangda Tan commented on YARN-3388: -- Hi [~nroberts], Sorry for my late response and thanks

[jira] [Commented] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

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

[jira] [Commented] (YARN-3318) Create Initial OrderingPolicy Framework, integrate with CapacityScheduler LeafQueue supporting present behavior

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387544#comment-14387544 ] Wangda Tan commented on YARN-3318: -- Hi Craig, Thanks for working on the patch, I just took

[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 ] Wangda Tan updated YARN-3388: - Summary: Allocation in LeafQueue could get stuck because DRF calculator isn't well supported when

[jira] [Commented] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387566#comment-14387566 ] Sangjin Lee commented on YARN-3334: --- Per Zhijie's suggestion, sounds like this code will

[jira] [Updated] (YARN-2890) MiniMRYarnCluster should turn on timeline service if configured to do so

[ https://issues.apache.org/jira/browse/YARN-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-2890: Attachment: YARN-2890.3.patch Removed debug statements. MiniMRYarnCluster should turn on timeline service

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387509#comment-14387509 ] Junping Du commented on YARN-3304: -- Let's do here. I will upload a quick patch soon.

[jira] [Reopened] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah reopened YARN-3304: --- Also, FWIW, ResourceCalculatorProcessTree is a public API. Re-opening as this breaks Tez ( again ).

[jira] [Commented] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387462#comment-14387462 ] Zhijie Shen commented on YARN-3391: --- bq. Then we can apply default values for all (name

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387478#comment-14387478 ] Vinod Kumar Vavilapalli commented on YARN-3304: --- To summarize what happened

[jira] [Commented] (YARN-2890) MiniMRYarnCluster should turn on timeline service if configured to do so

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

[jira] [Commented] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387561#comment-14387561 ] Sangjin Lee commented on YARN-3334: --- I'm +1 with the simpler approach mentioned here.

[jira] [Updated] (YARN-2243) Order of arguments for Preconditions.checkNotNull() is wrong in SchedulerApplicationAttempt ctor

[ https://issues.apache.org/jira/browse/YARN-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-2243: --- Fix Version/s: 2.7.0 Order of arguments for Preconditions.checkNotNull() is wrong in

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387585#comment-14387585 ] Karthik Kambatla commented on YARN-3304: [~vinodkv], [~hitesh] - given we have made

[jira] [Commented] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387463#comment-14387463 ] Sangjin Lee commented on YARN-3334: --- Sorry it took a while for me to go over the patch. I

[jira] [Commented] (YARN-2890) MiniMRYarnCluster should turn on timeline service if configured to do so

[ https://issues.apache.org/jira/browse/YARN-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387464#comment-14387464 ] Mit Desai commented on YARN-2890: - [~hitesh], the test failures were due to HADOOP-11754

[jira] [Commented] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387498#comment-14387498 ] Li Lu commented on YARN-3334: - Hi [~sjlee0], I have some quick questions about

[jira] [Commented] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387515#comment-14387515 ] Zhijie Shen commented on YARN-3391: --- bq. do you know of any such config or context

[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-tabpanelfocusedCommentId=14387556#comment-14387556 ] Wangda Tan commented on YARN-3388: -- Updated description. Allocation in LeafQueue could

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

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

[jira] [Updated] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3347: Summary: Improve YARN log command to get AMContainer logs as well as running containers logs (was: Improve

[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-tabpanelfocusedCommentId=14387713#comment-14387713 ] Hadoop QA commented on YARN-2729: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3391: -- Attachment: YARN-3391.1.patch Create a patch to fix the flow context info. I've updated the distributed

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387786#comment-14387786 ] Allen Wittenauer commented on YARN-3304: bq. To change tez, we will need to create

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14387825#comment-14387825 ] Hadoop QA commented on YARN-2740: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-appendix.patch Upload an appendix patch to address [~hitesh] and [~vinodkv]'s

[jira] [Commented] (YARN-3416) deadlock in a job between map and reduce cores allocation

[ https://issues.apache.org/jira/browse/YARN-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387838#comment-14387838 ] mai shurong commented on YARN-3416: --- mapreduce.job.reduce.slowstart.completedmaps is 0.5

  1   2   >