[jira] [Updated] (YARN-2768) Avoid cloning Resource in FSAppAttempt#updateDemand

[ https://issues.apache.org/jira/browse/YARN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2768: --- Summary: Avoid cloning Resource in FSAppAttempt#updateDemand (was: Avoid cloning Resource in

[jira] [Updated] (YARN-2768) Avoid cloning Resource in FSAppAttempt.updateDemand

[ https://issues.apache.org/jira/browse/YARN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2768: --- Summary: Avoid cloning Resource in FSAppAttempt.updateDemand (was: optimize

[jira] [Updated] (YARN-3919) NPEs' while stopping service after exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3919: Attachment: 0003-YARN-3919.patch The current patch not able to apply in my machine. So

[jira] [Commented] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

[ https://issues.apache.org/jira/browse/YARN-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646344#comment-14646344 ] Robert Kanter commented on YARN-3950: - Thanks! Add unique SHELL_ID environment

[jira] [Commented] (YARN-3989) Show messages only for NodeLabel commmands in RMAdminCLI

[ https://issues.apache.org/jira/browse/YARN-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646361#comment-14646361 ] Bibin A Chundatt commented on YARN-3989: [~sunilg] and [~Naganarasimha] Currently

[jira] [Commented] (YARN-2768) optimize FSAppAttempt.updateDemand by avoid clone of Resource which takes 85% of computing time of update thread

[ https://issues.apache.org/jira/browse/YARN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646374#comment-14646374 ] Karthik Kambatla commented on YARN-2768: +1 optimize FSAppAttempt.updateDemand by

[jira] [Resolved] (YARN-2768) Avoid cloning Resource in FSAppAttempt#updateDemand

[ https://issues.apache.org/jira/browse/YARN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-2768. Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.8.0 Just committed to

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646465#comment-14646465 ] Li Lu commented on YARN-3049: - Thanks [~zjshen]! For now I think it's fine to include the

[jira] [Commented] (YARN-1643) Make ContainersMonitor can support change monitoring size of an allocated container in NM side

[ https://issues.apache.org/jira/browse/YARN-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646403#comment-14646403 ] MENG DING commented on YARN-1643: - Thanks [~jianhe] for the review: bq. Here, memory *

[jira] [Assigned] (YARN-3991) Investigate if we need an atomic way to set both memory and CPU on Resource

[ https://issues.apache.org/jira/browse/YARN-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reassigned YARN-3991: -- Assignee: Varun Saxena Investigate if we need an atomic way to set both memory and CPU on

[jira] [Commented] (YARN-3992) TestApplicationPriority.testApplicationPriorityAllocation fails intermittently

[ https://issues.apache.org/jira/browse/YARN-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646454#comment-14646454 ] Sunil G commented on YARN-3992: --- Thank you [~zjshen] for reporting the same. I will take a

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646339#comment-14646339 ] Zhijie Shen commented on YARN-3049: ---

[jira] [Commented] (YARN-3992) TestApplicationPriority.testApplicationPriorityAllocation fails intermittently

[ https://issues.apache.org/jira/browse/YARN-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646443#comment-14646443 ] Zhijie Shen commented on YARN-3992: --- The problem was found with jenkins build on

[jira] [Commented] (YARN-3992) TestApplicationPriority.testApplicationPriorityAllocation fails intermittently

[ https://issues.apache.org/jira/browse/YARN-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646452#comment-14646452 ] Sunil G commented on YARN-3992: --- Thank you [~zhi

[jira] [Commented] (YARN-2768) Avoid cloning Resource in FSAppAttempt#updateDemand

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

[jira] [Commented] (YARN-3950) Add unique SHELL_ID environment variable to DistributedShell

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

[jira] [Updated] (YARN-3950) Add unique YARN_SHELL_ID environment variable to DistributedShell

[ https://issues.apache.org/jira/browse/YARN-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-3950: --- Summary: Add unique YARN_SHELL_ID environment variable to DistributedShell (was: Add unique

[jira] [Created] (YARN-3991) Investigate if we need an atomic way to set both memory and CPU on Resource

Karthik Kambatla created YARN-3991: -- Summary: Investigate if we need an atomic way to set both memory and CPU on Resource Key: YARN-3991 URL: https://issues.apache.org/jira/browse/YARN-3991 Project:

[jira] [Updated] (YARN-3991) Investigate if we need an atomic way to set both memory and CPU on Resource

[ https://issues.apache.org/jira/browse/YARN-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3991: --- Labels: capacityscheduler fairscheduler scheduler (was: ) Investigate if we need an atomic

[jira] [Commented] (YARN-3919) NPEs' while stopping service after exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646415#comment-14646415 ] Varun Saxena commented on YARN-3919: [~rohithsharma], are you using {{patch -p0}}

[jira] [Commented] (YARN-3919) NPEs' while stopping service after exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646448#comment-14646448 ] Rohith Sharma K S commented on YARN-3919: - No... git apply --whitespace=fix

[jira] [Commented] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646449#comment-14646449 ] zhihai xu commented on YARN-3990: - Yes, that is a good catch! {{rmContext.getRMApps()}}

[jira] [Created] (YARN-3992) TestApplicationPriority.testApplicationPriorityAllocation fails intermittently

Zhijie Shen created YARN-3992: - Summary: TestApplicationPriority.testApplicationPriorityAllocation fails intermittently Key: YARN-3992 URL: https://issues.apache.org/jira/browse/YARN-3992 Project: Hadoop

[jira] [Assigned] (YARN-3992) TestApplicationPriority.testApplicationPriorityAllocation fails intermittently

[ https://issues.apache.org/jira/browse/YARN-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-3992: - Assignee: Sunil G TestApplicationPriority.testApplicationPriorityAllocation fails intermittently

[jira] [Commented] (YARN-3919) NPEs' while stopping service after exception during CommonNodeLabelsManager#start

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

[jira] [Commented] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646566#comment-14646566 ] Anubhav Dhoot commented on YARN-3990: - Change looks good. It would be good to have a

[jira] [Commented] (YARN-3983) Make CapacityScheduler to easier extend application allocation logic

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

[jira] [Commented] (YARN-3994) RM should respect AM resource/placement constraints

[ https://issues.apache.org/jira/browse/YARN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646756#comment-14646756 ] Anubhav Dhoot commented on YARN-3994: - This jira should incorporate support for

[jira] [Commented] (YARN-1643) Make ContainersMonitor can support change monitoring size of an allocated container in NM side

[ https://issues.apache.org/jira/browse/YARN-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646709#comment-14646709 ] MENG DING commented on YARN-1643: - bq. IIUC, the main benefit is that we don't need to

[jira] [Updated] (YARN-3974) Refactor the reservation system test cases to use parameterized base test

[ https://issues.apache.org/jira/browse/YARN-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-3974: - Attachment: YARN-3974-v4.patch Uploading an updated patch that fixes the checkstyle issue

[jira] [Assigned] (YARN-3994) RM should respect AM resource/placement constraints

[ https://issues.apache.org/jira/browse/YARN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reassigned YARN-3994: --- Assignee: Varun Vasudev RM should respect AM resource/placement constraints

[jira] [Commented] (YARN-3979) Am in ResourceLocalizationService hang 10 min cause RM kill AM

[ https://issues.apache.org/jira/browse/YARN-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646510#comment-14646510 ] Rohith Sharma K S commented on YARN-3979: - Oops, 50 lakh events I checked the

[jira] [Created] (YARN-3993) Change to use the AM flag in ContainerContext determine AM container

Zhijie Shen created YARN-3993: - Summary: Change to use the AM flag in ContainerContext determine AM container Key: YARN-3993 URL: https://issues.apache.org/jira/browse/YARN-3993 Project: Hadoop YARN

[jira] [Updated] (YARN-3919) NPEs' while stopping service after exception during CommonNodeLabelsManager#start

[ https://issues.apache.org/jira/browse/YARN-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3919: Priority: Trivial (was: Major) NPEs' while stopping service after exception during

[jira] [Commented] (YARN-3993) Change to use the AM flag in ContainerContext determine AM container

[ https://issues.apache.org/jira/browse/YARN-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646559#comment-14646559 ] Sunil G commented on YARN-3993: --- OK. I understood slightly different. With the new changes

[jira] [Updated] (YARN-3993) Change to use the AM flag in ContainerContext determine AM container

[ https://issues.apache.org/jira/browse/YARN-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3993: -- Labels: newbie (was: ) Change to use the AM flag in ContainerContext determine AM container

[jira] [Comment Edited] (YARN-3993) Change to use the AM flag in ContainerContext determine AM container

[ https://issues.apache.org/jira/browse/YARN-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646558#comment-14646558 ] Zhijie Shen edited comment on YARN-3993 at 7/29/15 6:26 PM:

[jira] [Commented] (YARN-3994) RM should respect AM resource/placement constraints

[ https://issues.apache.org/jira/browse/YARN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646707#comment-14646707 ] Wangda Tan commented on YARN-3994: -- +1 for this, we should target this to 2.8. RM should

[jira] [Commented] (YARN-3250) Support admin/user cli interface in for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646490#comment-14646490 ] Rohith Sharma K S commented on YARN-3250: - Adding to User API discussion, the

[jira] [Commented] (YARN-3919) NPEs' while stopping service after exception during CommonNodeLabelsManager#start

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

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646556#comment-14646556 ] Xuan Gong commented on YARN-3543: - Sorry for the late. The patch looks good overall. But we

[jira] [Updated] (YARN-3994) RM should respect AM resource/placement constraints

[ https://issues.apache.org/jira/browse/YARN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3994: - Target Version/s: 2.8.0 RM should respect AM resource/placement constraints

[jira] [Commented] (YARN-3887) Support for changing Application priority during runtime

[ https://issues.apache.org/jira/browse/YARN-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646676#comment-14646676 ] Jian He commented on YARN-3887: --- sounds good to me Support for changing Application

[jira] [Assigned] (YARN-3993) Change to use the AM flag in ContainerContext determine AM container

[ https://issues.apache.org/jira/browse/YARN-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-3993: - Assignee: Sunil G Change to use the AM flag in ContainerContext determine AM container

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646598#comment-14646598 ] Rohith Sharma K S commented on YARN-3543: - I got what you mean!! Right.. Modifying

[jira] [Commented] (YARN-3978) Configurably turn off the saving of container info in Generic AHS

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

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646700#comment-14646700 ] Bikas Saha commented on YARN-2005: -- I am fine for opening a separate jira for the specific

[jira] [Created] (YARN-3994) RM should respect AM resource/placement constraints

Bikas Saha created YARN-3994: Summary: RM should respect AM resource/placement constraints Key: YARN-3994 URL: https://issues.apache.org/jira/browse/YARN-3994 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-3993) Change to use the AM flag in ContainerContext determine AM container

[ https://issues.apache.org/jira/browse/YARN-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646532#comment-14646532 ] Sunil G commented on YARN-3993: --- Hi [~zjshen] In SchedulerApplicationAttempt,we can use

[jira] [Updated] (YARN-3992) TestApplicationPriority.testApplicationPriorityAllocation fails intermittently

[ https://issues.apache.org/jira/browse/YARN-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3992: -- Attachment: 0001-YARN-3992.patch Thank you [~zjshen]. It seems we were not waiting for full containers to get

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646612#comment-14646612 ] Anubhav Dhoot commented on YARN-2005: - I think blacklisting can have lots of policies

[jira] [Commented] (YARN-3992) TestApplicationPriority.testApplicationPriorityAllocation fails intermittently

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

[jira] [Updated] (YARN-3993) Change to use the AM flag in ContainerContext determine AM container

[ https://issues.apache.org/jira/browse/YARN-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-3993: -- Affects Version/s: YARN-2928 Change to use the AM flag in ContainerContext determine AM container

[jira] [Updated] (YARN-3983) Make CapacityScheduler to easier extend application allocation logic

[ https://issues.apache.org/jira/browse/YARN-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3983: - Attachment: YARN-3983.1.patch Attached initial patch for review. Make CapacityScheduler to easier extend

[jira] [Commented] (YARN-3250) Support admin/user cli interface in for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646478#comment-14646478 ] Rohith Sharma K S commented on YARN-3250: - Hi [~sunilg] As part of this JIRA, #

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646568#comment-14646568 ] Rohith Sharma K S commented on YARN-3543: - Thanks [~xgong] for review.. bq. But we

[jira] [Commented] (YARN-3127) Avoid timeline events during RM recovery or restart

[ https://issues.apache.org/jira/browse/YARN-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646668#comment-14646668 ] Naganarasimha G R commented on YARN-3127: - Hi [~xgong], [~gtCarrera] [~ozawa], Can

[jira] [Commented] (YARN-3250) Support admin/user cli interface in for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646495#comment-14646495 ] Rohith Sharma K S commented on YARN-3250: - small correction in above syntax.

[jira] [Commented] (YARN-3250) Support admin/user cli interface in for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646518#comment-14646518 ] Sunil G commented on YARN-3250: --- Hi [~rohithsharma] Thank you for bringing up with api

[jira] [Commented] (YARN-3993) Change to use the AM flag in ContainerContext determine AM container

[ https://issues.apache.org/jira/browse/YARN-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646558#comment-14646558 ] Zhijie Shen commented on YARN-3993: --- [~sunilg], thanks for your interest. It's not

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646622#comment-14646622 ] Rohith Sharma K S commented on YARN-3543: - I have one doubt that whether it is able

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646893#comment-14646893 ] Li Lu commented on YARN-3049: - Hi [~zjshen], some of my comments: - The addition on {{newApp}}

[jira] [Commented] (YARN-3974) Refactor the reservation system test cases to use parameterized base test

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

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646924#comment-14646924 ] Zhijie Shen commented on YARN-3984: --- [~vrushalic], thanks for picking it up. The

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646930#comment-14646930 ] Sangjin Lee commented on YARN-3984: --- {quote} In addition to the key composition, I find

[jira] [Updated] (YARN-3904) Refactor timelineservice.storage to add support to online and offline aggregation writers

[ https://issues.apache.org/jira/browse/YARN-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3904: Attachment: YARN-3904-YARN-2928.005.patch Refreshed my patch according to [~sjlee0]'s comments. Specifically, I set

[jira] [Commented] (YARN-3814) REST API implementation for getting raw entities in TimelineReader

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

[jira] [Updated] (YARN-3994) RM should respect AM resource/placement constraints

[ https://issues.apache.org/jira/browse/YARN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3994: Assignee: (was: Varun Vasudev) RM should respect AM resource/placement constraints

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646935#comment-14646935 ] Zhijie Shen commented on YARN-3984: --- In fact, metric has the same problem, but it may be

[jira] [Commented] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646975#comment-14646975 ] Wangda Tan commented on YARN-3945: -- And forgot to mention, maxApplicationsPerUser

[jira] [Commented] (YARN-3995) Some of the NM events are not getting published due race condition when AM container finishes in NM

[ https://issues.apache.org/jira/browse/YARN-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647017#comment-14647017 ] Naganarasimha G R commented on YARN-3995: - Two approaches were discussed till now :

[jira] [Commented] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646964#comment-14646964 ] Wangda Tan commented on YARN-3945: -- Thanks for summarizing [~Naganarasimha]. I think we

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14646992#comment-14646992 ] Naganarasimha G R commented on YARN-3045: - Thanks for the comments [~djp], bq. We

[jira] [Created] (YARN-3996) YARN-789 (Support for zero capabilities in fairscheduler) is broken after YARN-3305

Anubhav Dhoot created YARN-3996: --- Summary: YARN-789 (Support for zero capabilities in fairscheduler) is broken after YARN-3305 Key: YARN-3996 URL: https://issues.apache.org/jira/browse/YARN-3996

[jira] [Commented] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647045#comment-14647045 ] Arun Suresh commented on YARN-3920: --- Thanks for the patch [~adhoot], The patch looks

[jira] [Commented] (YARN-3974) Refactor the reservation system test cases to use parameterized base test

[ https://issues.apache.org/jira/browse/YARN-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647070#comment-14647070 ] Anubhav Dhoot commented on YARN-3974: - LGTM Refactor the reservation system test

[jira] [Commented] (YARN-3979) Am in ResourceLocalizationService hang 10 min cause RM kill AM

[ https://issues.apache.org/jira/browse/YARN-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647095#comment-14647095 ] zhangyubiao commented on YARN-3979: --- the cluster is about 1600。and about 550 apps

[jira] [Commented] (YARN-3904) Refactor timelineservice.storage to add support to online and offline aggregation writers

[ https://issues.apache.org/jira/browse/YARN-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647132#comment-14647132 ] Li Lu commented on YARN-3904: - The two failed tests passed on my local machine, and the

[jira] [Commented] (YARN-3979) Am in ResourceLocalizationService hang 10 min cause RM kill AM

[ https://issues.apache.org/jira/browse/YARN-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647130#comment-14647130 ] zhangyubiao commented on YARN-3979: --- I had send you an email of RM Jstack log and I wil

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14647163#comment-14647163 ] Sangjin Lee commented on YARN-3045: --- bq. I went through the discussions and the patch of

[jira] [Commented] (YARN-2884) Proxying all AM-RM communications

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

[jira] [Commented] (YARN-3979) Am in ResourceLocalizationService hang 10 min cause RM kill AM

[ https://issues.apache.org/jira/browse/YARN-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647177#comment-14647177 ] Rohith Sharma K S commented on YARN-3979: - Thanks for the information!! bq.

[jira] [Commented] (YARN-3904) Refactor timelineservice.storage to add support to online and offline aggregation writers

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

[jira] [Commented] (YARN-3983) Make CapacityScheduler to easier extend application allocation logic

[ https://issues.apache.org/jira/browse/YARN-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647150#comment-14647150 ] Jian He commented on YARN-3983: --- thanks Wangda ! some comments on the patch -

[jira] [Created] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected

Rohith Sharma K S created YARN-3990: --- Summary: AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected Key: YARN-3990 URL: https://issues.apache.org/jira/browse/YARN-3990

[jira] [Commented] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645795#comment-14645795 ] Bibin A Chundatt commented on YARN-3990: [~rohithsharma] Yes,Currently i have

[jira] [Commented] (YARN-3979) Am in ResourceLocalizationService hang 10 min cause RM kill AM

[ https://issues.apache.org/jira/browse/YARN-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645601#comment-14645601 ] zhangyubiao commented on YARN-3979: --- Thank you for reply @Rohith Sharma K S Am in

[jira] [Updated] (YARN-3979) Am in ResourceLocalizationService hang 10 min cause RM kill AM

[ https://issues.apache.org/jira/browse/YARN-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangyubiao updated YARN-3979: -- Attachment: ERROR103.log the RM Log is so large So I grep ERROR for logs Am in

[jira] [Updated] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3990: Summary: AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is

[jira] [Assigned] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt reassigned YARN-3990: -- Assignee: Bibin A Chundatt AsyncDispatcher may overloaded with RMAppNodeUpdateEvent

[jira] [Updated] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3990: --- Attachment: 0001-YARN-3990.patch [~rohithsharma] Attaching patch for initial review

[jira] [Commented] (YARN-3979) Am in ResourceLocalizationService hang 10 min cause RM kill AM

[ https://issues.apache.org/jira/browse/YARN-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645535#comment-14645535 ] Rohith Sharma K S commented on YARN-3979: - How many applications completed? How

[jira] [Commented] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645567#comment-14645567 ] Bibin A Chundatt commented on YARN-3990: [~rohithsharma] {code} 2015-07-29

[jira] [Commented] (YARN-3887) Support for changing Application priority during runtime

[ https://issues.apache.org/jira/browse/YARN-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645566#comment-14645566 ] Rohith Sharma K S commented on YARN-3887: - Your understanding is correct. I was

[jira] [Commented] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645583#comment-14645583 ] Rohith Sharma K S commented on YARN-3990: - thanks [~bibinchundatt] for reproducing

[jira] [Updated] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3945: Attachment: YARN-3945.20150729-1.patch Oops My Mistake, corrected the patch to remove javac

[jira] [Commented] (YARN-3989) Show messages only for NodeLabel commmands in RMAdminCLI

[ https://issues.apache.org/jira/browse/YARN-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645870#comment-14645870 ] Naganarasimha G R commented on YARN-3989: - hi [~bibinchundatt] [~sunilg], Is the

[jira] [Commented] (YARN-3945) maxApplicationsPerUser is wrongly calculated

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

[jira] [Commented] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

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

[jira] [Commented] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646048#comment-14646048 ] Naganarasimha G R commented on YARN-3945: - [~wangda] [~nroberts], Checkstyle is

  1   2   >