[jira] [Commented] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

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

[jira] [Commented] (YARN-1003) Add a maxContainersPerNode config to the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726089#comment-13726089 ] Vinod Kumar Vavilapalli commented on YARN-1003: --- Why is this needed? We

[jira] [Commented] (YARN-1003) Add a maxContainersPerNode config to the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726095#comment-13726095 ] Karthik Kambatla commented on YARN-1003: One of the most common questions we hear

[jira] [Commented] (YARN-1003) Add a maxContainersPerNode config to the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726100#comment-13726100 ] Sandy Ryza commented on YARN-1003: -- This makes it so that we don't need to use the

[jira] [Commented] (YARN-1003) Add a maxContainersPerNode config to the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726101#comment-13726101 ] Vinod Kumar Vavilapalli commented on YARN-1003: --- I guess you are referring to

[jira] [Commented] (YARN-1003) Add a maxContainersPerNode config to the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726111#comment-13726111 ] Sandy Ryza commented on YARN-1003: -- My thinking was not per job. Agreed that the way to

[jira] [Commented] (YARN-758) Augment MockNM to use multiple cores

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

[jira] [Updated] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1004: - Attachment: YARN-1004.patch yarn.scheduler.minimum|maximum|increment-allocation-mb should have

[jira] [Commented] (YARN-1003) Add a maxContainersPerNode config to the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726118#comment-13726118 ] Vinod Kumar Vavilapalli commented on YARN-1003: --- bq. This makes it so that we

[jira] [Reopened] (YARN-758) Augment MockNM to use multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened YARN-758: -- Our test-patch is not smart enough, there isn't any test in the patch but it didn't

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726122#comment-13726122 ] Sandy Ryza commented on YARN-1004: -- Uploaded a patch that adds fair, capacity, and fifo to

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726124#comment-13726124 ] Sandy Ryza commented on YARN-1004: -- By which I mean [~tucu00]

[jira] [Commented] (YARN-758) Augment MockNM to use multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726163#comment-13726163 ] Karthik Kambatla commented on YARN-758: --- I should have explicitly stated how I tested

[jira] [Updated] (YARN-906) Cancelling ContainerLaunch#call at KILLING causes that the container cannot be completed

[ https://issues.apache.org/jira/browse/YARN-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-906: - Attachment: YARN-906.5.patch Thanks Vinod for the suggestions. Uploaded the new patch. bq. When a

[jira] [Commented] (YARN-906) Cancelling ContainerLaunch#call at KILLING causes that the container cannot be completed

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

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler

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

[jira] [Commented] (YARN-956) [YARN-321] Add History Store interface and testable in-memory HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726204#comment-13726204 ] Mayank Bansal commented on YARN-956: Thanks [~vinodkv] and [~zjshen] for review. I am

[jira] [Updated] (YARN-956) [YARN-321] Add History Store interface and testable in-memory HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-956: --- Attachment: YARN-956-3.patch Attaching patch Thanks, Mayank [YARN-321] Add History

[jira] [Commented] (YARN-956) [YARN-321] Add History Store interface and testable in-memory HistoryStorage

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

[jira] [Commented] (YARN-758) Augment MockNM to use multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726321#comment-13726321 ] Hudson commented on YARN-758: - SUCCESS: Integrated in Hadoop-Yarn-trunk #288 (See

[jira] [Commented] (YARN-502) RM crash with NPE on NODE_REMOVED event with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726323#comment-13726323 ] Hudson commented on YARN-502: - SUCCESS: Integrated in Hadoop-Yarn-trunk #288 (See

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726380#comment-13726380 ] Steve Loughran commented on YARN-972: - bq. Nodes in probably the majority of clusters

[jira] [Commented] (YARN-758) Augment MockNM to use multiple cores

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

[jira] [Commented] (YARN-502) RM crash with NPE on NODE_REMOVED event with FairScheduler

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

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726452#comment-13726452 ] Jason Lowe commented on YARN-972: - bq. What could work is for a YARN app to be able to say

[jira] [Commented] (YARN-758) Augment MockNM to use multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726455#comment-13726455 ] Hudson commented on YARN-758: - SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1505 (See

[jira] [Created] (YARN-1007) [YARN-321] Enhance History Reader interface for Containers

Devaraj K created YARN-1007: --- Summary: [YARN-321] Enhance History Reader interface for Containers Key: YARN-1007 URL: https://issues.apache.org/jira/browse/YARN-1007 Project: Hadoop YARN Issue

[jira] [Assigned] (YARN-1007) [YARN-321] Enhance History Reader interface for Containers

[ https://issues.apache.org/jira/browse/YARN-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K reassigned YARN-1007: --- Assignee: (was: Devaraj K) [YARN-321] Enhance History Reader interface for Containers

[jira] [Created] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

Alejandro Abdelnur created YARN-1008: Summary: MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations Key: YARN-1008 URL: https://issues.apache.org/jira/browse/YARN-1008

[jira] [Created] (YARN-1009) Scheduler configuration properties should be prefixed with the scheduler type

Alejandro Abdelnur created YARN-1009: Summary: Scheduler configuration properties should be prefixed with the scheduler type Key: YARN-1009 URL: https://issues.apache.org/jira/browse/YARN-1009

[jira] [Created] (YARN-1010) FairScheduler: decouple container scheduling from nodemanager heartbeats

Alejandro Abdelnur created YARN-1010: Summary: FairScheduler: decouple container scheduling from nodemanager heartbeats Key: YARN-1010 URL: https://issues.apache.org/jira/browse/YARN-1010

[jira] [Commented] (YARN-1003) Add a maxContainersPerNode config to the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726586#comment-13726586 ] Sandy Ryza commented on YARN-1003: -- bq. this can be done by being conservative on the

[jira] [Commented] (YARN-1009) Scheduler configuration properties should be prefixed with the scheduler type

[ https://issues.apache.org/jira/browse/YARN-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726590#comment-13726590 ] Sandy Ryza commented on YARN-1009: -- Is this a duplicate of YARN-1004?

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726595#comment-13726595 ] Sandy Ryza commented on YARN-972: - Meant: That's why I say (3) and (4) should be non-goals.

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726594#comment-13726594 ] Sandy Ryza commented on YARN-972: - bq. Determinism isn't something you can get with other

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726610#comment-13726610 ] Bikas Saha commented on YARN-972: - An approach that has been successfully used elsewhere is

[jira] [Commented] (YARN-573) Shared data structures in Public Localizer and Private Localizer are not Thread safe.

[ https://issues.apache.org/jira/browse/YARN-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726619#comment-13726619 ] Sangjin Lee commented on YARN-573: -- The new patch looks good to me. Thanks!

[jira] [Commented] (YARN-1010) FairScheduler: decouple container scheduling from nodemanager heartbeats

[ https://issues.apache.org/jira/browse/YARN-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726694#comment-13726694 ] Omkar Vinit Joshi commented on YARN-1010: - probably this should be done

[jira] [Commented] (YARN-1007) [YARN-321] Enhance History Reader interface for Containers

[ https://issues.apache.org/jira/browse/YARN-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726697#comment-13726697 ] Mayank Bansal commented on YARN-1007: - Taking it over as these are the reader interface

[jira] [Assigned] (YARN-1007) [YARN-321] Enhance History Reader interface for Containers

[ https://issues.apache.org/jira/browse/YARN-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal reassigned YARN-1007: --- Assignee: Mayank Bansal [YARN-321] Enhance History Reader interface for Containers

[jira] [Commented] (YARN-1010) FairScheduler: decouple container scheduling from nodemanager heartbeats

[ https://issues.apache.org/jira/browse/YARN-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726704#comment-13726704 ] Sandy Ryza commented on YARN-1010: -- Agreed that it would be a good change to include in

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726705#comment-13726705 ] Omkar Vinit Joshi commented on YARN-713: Creating patch on top of YARN-957

[jira] [Created] (YARN-1011) RM should dynamically schedule containers based on utilization of currently allocated containers

Arun C Murthy created YARN-1011: --- Summary: RM should dynamically schedule containers based on utilization of currently allocated containers Key: YARN-1011 URL: https://issues.apache.org/jira/browse/YARN-1011

[jira] [Commented] (YARN-1007) [YARN-321] Enhance History Reader interface for Containers

[ https://issues.apache.org/jira/browse/YARN-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726709#comment-13726709 ] Mayank Bansal commented on YARN-1007: - [~devaraj.k], Please look into YARN-956, I

[jira] [Created] (YARN-1012) NM should report resource utilization of running containers to RM in heartbeat

Arun C Murthy created YARN-1012: --- Summary: NM should report resource utilization of running containers to RM in heartbeat Key: YARN-1012 URL: https://issues.apache.org/jira/browse/YARN-1012 Project:

[jira] [Created] (YARN-1013) CS should watch resource utilization of containers and allocate speculative containers if appropriate

Arun C Murthy created YARN-1013: --- Summary: CS should watch resource utilization of containers and allocate speculative containers if appropriate Key: YARN-1013 URL: https://issues.apache.org/jira/browse/YARN-1013

[jira] [Commented] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

[ https://issues.apache.org/jira/browse/YARN-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726713#comment-13726713 ] Bikas Saha commented on YARN-994: - Code change looks good. The new test is a copy paste of

[jira] [Created] (YARN-1014) Enhance LCE to support cgroups for speculative containers at lower priorities

Arun C Murthy created YARN-1014: --- Summary: Enhance LCE to support cgroups for speculative containers at lower priorities Key: YARN-1014 URL: https://issues.apache.org/jira/browse/YARN-1014 Project:

[jira] [Updated] (YARN-1011) [Umbrella] RM should dynamically schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1011: Summary: [Umbrella] RM should dynamically schedule containers based on utilization of currently

[jira] [Updated] (YARN-903) DistributedShell throwing Errors in logs after successfull completion

[ https://issues.apache.org/jira/browse/YARN-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-903: --- Attachment: YARN-903-20130801.1.patch DistributedShell throwing Errors in logs after

[jira] [Created] (YARN-1015) FS should watch resource utilization of containers and allocate speculative containers if appropriate

Arun C Murthy created YARN-1015: --- Summary: FS should watch resource utilization of containers and allocate speculative containers if appropriate Key: YARN-1015 URL: https://issues.apache.org/jira/browse/YARN-1015

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726718#comment-13726718 ] Arun C Murthy commented on YARN-972: Agree with Jason Bikas - I've been noodling

[jira] [Updated] (YARN-1015) FS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1015: Assignee: (was: Arun C Murthy) FS should watch resource utilization of containers and

[jira] [Updated] (YARN-1015) FS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1015: Description: FS should watch resource utilization of containers (provided by NM in heartbeat) and

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726726#comment-13726726 ] Sandy Ryza commented on YARN-972: - Agreed that speculative containers will be an awesome

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726740#comment-13726740 ] Jian He commented on YARN-643: -- Few comments on the patch: - The tokens are first removed

[jira] [Commented] (YARN-903) DistributedShell throwing Errors in logs after successfull completion

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

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726750#comment-13726750 ] Omkar Vinit Joshi commented on YARN-713: * Today we are generating ContainerToken

[jira] [Commented] (YARN-573) Shared data structures in Public Localizer and Private Localizer are not Thread safe.

[ https://issues.apache.org/jira/browse/YARN-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726776#comment-13726776 ] Jason Lowe commented on YARN-573: - +1, lgtm as well. Committing this.

[jira] [Commented] (YARN-573) Shared data structures in Public Localizer and Private Localizer are not Thread safe.

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

[jira] [Updated] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

[ https://issues.apache.org/jira/browse/YARN-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-994: --- Attachment: YARN-994.3.patch HeartBeat thread in AMRMClientAsync does not handle runtime exception

[jira] [Commented] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

[ https://issues.apache.org/jira/browse/YARN-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726800#comment-13726800 ] Xuan Gong commented on YARN-994: Yes, new patch will fix this HeartBeat

[jira] [Commented] (YARN-956) [YARN-321] Add History Store interface and testable in-memory HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726873#comment-13726873 ] Zhijie Shen commented on YARN-956: -- One more thought about HistoryStorage. Does

[jira] [Commented] (YARN-953) [YARN-321] Change ResourceManager to use HistoryStorage to log history data

[ https://issues.apache.org/jira/browse/YARN-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726898#comment-13726898 ] Zhijie Shen commented on YARN-953: -- bq. Instead of adding a new

[jira] [Commented] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

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

[jira] [Commented] (YARN-956) [YARN-321] Add History Store interface and testable in-memory HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726956#comment-13726956 ] Mayank Bansal commented on YARN-956: Its intresting however not sure if we absolutely

[jira] [Commented] (YARN-1011) [Umbrella] RM should dynamically schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726965#comment-13726965 ] Bikas Saha commented on YARN-1011: -- An approach that has been successfully used elsewhere

[jira] [Updated] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-643: --- Attachment: YARN-643.3.patch WHY appToken is removed both in BaseFinalTransition and

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726968#comment-13726968 ] Xuan Gong commented on YARN-643: Thanks for the comments. Update the patch

[jira] [Commented] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

[ https://issues.apache.org/jira/browse/YARN-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726972#comment-13726972 ] Bikas Saha commented on YARN-994: - +1. Thanks for the fix Xuan! Committing to trunk and

[jira] [Assigned] (YARN-1015) FS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1015: -- Assignee: Karthik Kambatla FS should watch resource utilization of containers and

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

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

[jira] [Commented] (YARN-758) Augment MockNM to use multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727002#comment-13727002 ] Karthik Kambatla commented on YARN-758: --- [~vinodkv], should we still keep this JIRA

[jira] [Reopened] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[ https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reopened YARN-978: Assignee: Xuan Gong (was: Mayank Bansal) [YARN-321] Adding ApplicationAttemptReport and Protobuf

[jira] [Commented] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[ https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727023#comment-13727023 ] Xuan Gong commented on YARN-978: Open the ticket. Trunk need this, too

[jira] [Updated] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[ https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-978: --- Attachment: YARN-978.2.patch [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[jira] [Commented] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

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

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727088#comment-13727088 ] Jian He commented on YARN-643: -- Patch mostly good, In the test case, can you also verify

[jira] [Updated] (YARN-573) Shared data structures in Public Localizer and Private Localizer are not Thread safe.

[ https://issues.apache.org/jira/browse/YARN-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-573: Fix Version/s: (was: 2.1.0-beta) 2.1.1-beta Shared data structures in Public

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-353: - Attachment: YARN-353.9.patch Uploaded a patch to fix comments and findbugs Add Zookeeper-based

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727128#comment-13727128 ] Alejandro Abdelnur commented on YARN-1004: -- Agree we should keep MAX as the only

[jira] [Updated] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-1004: - Priority: Blocker (was: Major)

[jira] [Commented] (YARN-573) Shared data structures in Public Localizer and Private Localizer are not Thread safe.

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

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

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

[jira] [Commented] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[ https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727188#comment-13727188 ] Xuan Gong commented on YARN-978: No test cases added [YARN-321] Adding

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727185#comment-13727185 ] Xuan Gong commented on YARN-643: bq.why we need to explicitly send the EXPIRE event, doesn't

[jira] [Created] (YARN-1016) Define a HDFS based repository that allows YARN services to share resources

Kam Kasravi created YARN-1016: - Summary: Define a HDFS based repository that allows YARN services to share resources Key: YARN-1016 URL: https://issues.apache.org/jira/browse/YARN-1016 Project: Hadoop

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727210#comment-13727210 ] Omkar Vinit Joshi commented on YARN-713: [~daryn] [~vinodkv] any reason why we are

[jira] [Updated] (YARN-1011) [Umbrella] RM should dynamically schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1011: Assignee: (was: Arun C Murthy) [Umbrella] RM should dynamically schedule containers based

[jira] [Created] (YARN-1017) Document RM Restart feature

Jian He created YARN-1017: - Summary: Document RM Restart feature Key: YARN-1017 URL: https://issues.apache.org/jira/browse/YARN-1017 Project: Hadoop YARN Issue Type: Sub-task Reporter: