[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.4.patch Fix the test failure. Cancelling ContainerLaunch#call at

[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=13724958#comment-13724958 ] Hadoop QA commented on YARN-906: {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-975) Adding HDFS implementation for Writing Interface of History Storage

[ https://issues.apache.org/jira/browse/YARN-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-975: - Attachment: YARN-975.1.patch Talked to Vinod. We should created a history storage that groups the reader

[jira] [Resolved] (YARN-946) Adding HDFS implementation for Histrory Reader Interface

[ https://issues.apache.org/jira/browse/YARN-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-946. -- Resolution: Duplicate Close the ticket as we decided to create the history storage which implement

[jira] [Updated] (YARN-975) Adding HDFS implementation for grouped reading and writing interfaces of history storage

[ https://issues.apache.org/jira/browse/YARN-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-975: - Summary: Adding HDFS implementation for grouped reading and writing interfaces of history storage (was:

[jira] [Created] (YARN-1002) Optimizing the reading/writing operations of FileSystemHistoryStorage

Zhijie Shen created YARN-1002: - Summary: Optimizing the reading/writing operations of FileSystemHistoryStorage Key: YARN-1002 URL: https://issues.apache.org/jira/browse/YARN-1002 Project: Hadoop YARN

[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=13724971#comment-13724971 ] Zhijie Shen commented on YARN-956: -- WRT ApplicationHistoryReader, do you think the APIs

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

Sandy Ryza created YARN-1003: Summary: Add a maxContainersPerNode config to the Fair Scheduler Key: YARN-1003 URL: https://issues.apache.org/jira/browse/YARN-1003 Project: Hadoop YARN Issue

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

Sandy Ryza created YARN-1004: Summary: yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler Key: YARN-1004 URL: https://issues.apache.org/jira/browse/YARN-1004 Project: Hadoop

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

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

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

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

[jira] [Commented] (YARN-770) NPE NodeStatusUpdaterImpl

[ https://issues.apache.org/jira/browse/YARN-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725109#comment-13725109 ] Steve Loughran commented on YARN-770: - I was just running a test which used a MiniYARN

[jira] [Commented] (YARN-445) Ability to signal containers

[ https://issues.apache.org/jira/browse/YARN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725111#comment-13725111 ] Steve Loughran commented on YARN-445: - I like Chris's #3 option, as it allows you to add

[jira] [Created] (YARN-1005) Log aggregators should check for FSDataOutputStream close before renaming to aggregated file.

Rohith Sharma K S created YARN-1005: --- Summary: Log aggregators should check for FSDataOutputStream close before renaming to aggregated file. Key: YARN-1005 URL: https://issues.apache.org/jira/browse/YARN-1005

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

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

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

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

[jira] [Commented] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

[ https://issues.apache.org/jira/browse/YARN-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725237#comment-13725237 ] Jason Lowe commented on YARN-107: - I still think throwing an exception for this is a mistake

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

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

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

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

[jira] [Commented] (YARN-602) NodeManager should mandatorily set some Environment variables into every containers that it launches

[ https://issues.apache.org/jira/browse/YARN-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725296#comment-13725296 ] Kenji Kikushima commented on YARN-602: -- Sorry, late for update and windows case error.

[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=13725299#comment-13725299 ] Hitesh Shah commented on YARN-1004: --- Is there a reason why maximum-allocation is also

[jira] [Commented] (YARN-997) JMX support for node resource configuration

[ https://issues.apache.org/jira/browse/YARN-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725310#comment-13725310 ] Junping Du commented on YARN-997: - I think Luke already address you previous question on

[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=13725372#comment-13725372 ] Steve Loughran commented on YARN-972: - I'd argue against fractional core assignment not

[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.2.patch WHY appToken is removed both in BaseFinalTransition and

[jira] [Updated] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

[ https://issues.apache.org/jira/browse/YARN-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-107: --- Attachment: YARN-107.3.patch Fix -1 release audit. ClientRMService.forceKillApplication()

[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=13725395#comment-13725395 ] Bikas Saha commented on YARN-1004: -- It would be sad to have deprecated configs when YARN

[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=13725426#comment-13725426 ] Allen Wittenauer commented on YARN-972: --- One other thing, before I forget... these

[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=13725423#comment-13725423 ] Hadoop QA commented on YARN-643: {color:green}+1 overall{color}. Here are the results of

[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=13725427#comment-13725427 ] Alejandro Abdelnur commented on YARN-972: - Allen, what you want seems to be

[jira] [Commented] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

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

[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=13725459#comment-13725459 ] Sandy Ryza commented on YARN-972: - [~ste...@apache.org], bq. Those caches are the key to

[jira] [Commented] (YARN-602) NodeManager should mandatorily set some Environment variables into every containers that it launches

[ https://issues.apache.org/jira/browse/YARN-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725475#comment-13725475 ] Vinod Kumar Vavilapalli commented on YARN-602: -- bq. How can I fix putting env

[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=13725476#comment-13725476 ] Sandy Ryza commented on YARN-1004: -- [~hitesh], maximum-allocation is just for consistency.

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725483#comment-13725483 ] Omkar Vinit Joshi commented on YARN-966: bq. One more consideration. Empty map can

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725489#comment-13725489 ] Omkar Vinit Joshi commented on YARN-966: So if user say kills the container what

[jira] [Assigned] (YARN-955) [YARN-321] History Service should create the RPC server and wire it to HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal reassigned YARN-955: -- Assignee: Mayank Bansal (was: Vinod Kumar Vavilapalli) [YARN-321] History Service should

[jira] [Updated] (YARN-987) Implementation of *HistoryData classes to convert to *Report Objects

[ https://issues.apache.org/jira/browse/YARN-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-987: --- Summary: Implementation of *HistoryData classes to convert to *Report Objects (was: Read Interface

[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=13725505#comment-13725505 ] Omkar Vinit Joshi commented on YARN-573: [~jlowe] Thanks for reviewing.. bq.

[jira] [Commented] (YARN-955) [YARN-321] History Service should create the RPC server and wire it to HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725506#comment-13725506 ] Mayank Bansal commented on YARN-955: Taking it over [YARN-321] History

[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 ] Omkar Vinit Joshi updated YARN-573: --- Description: PublicLocalizer 1) pending accessed by addResource (part of event handling) and

[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=13725517#comment-13725517 ] Hitesh Shah commented on YARN-1004: --- [~sandyr] Scheduler-specific configs are fine as

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725518#comment-13725518 ] Vinod Kumar Vavilapalli commented on YARN-966: -- bq. Potentially I don't see

[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=13725522#comment-13725522 ] Sandy Ryza commented on YARN-1004: -- [~hitesh], your reasoning makes sense to me. I'll

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725526#comment-13725526 ] Zhijie Shen commented on YARN-966: -- bq. Potentially I don't see when we will in fact start

[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=13725528#comment-13725528 ] Allen Wittenauer commented on YARN-972: --- bq. Nodes in probably the majority 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=13725530#comment-13725530 ] Vinod Kumar Vavilapalli commented on YARN-1004: --- bq. maximum-allocation 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=13725544#comment-13725544 ] Jason Lowe commented on YARN-573: - bq. I thought about it earlier but we are using iterator

[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=13725571#comment-13725571 ] Sangjin Lee commented on YARN-573: -- +1 on wrapping the list with

[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=13725556#comment-13725556 ] Hitesh Shah commented on YARN-1004: --- [~vinodkv] min allocation is no longer visible to an

[jira] [Commented] (YARN-985) Nodemanager should log where a resource was localized

[ https://issues.apache.org/jira/browse/YARN-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725610#comment-13725610 ] Ravi Prakash commented on YARN-985: --- Hi Omkar! bq. yeah this is a small thing but would

[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=13725652#comment-13725652 ] Arun C Murthy commented on YARN-972: I'll repeat what I said in YARN-2, this is a bad

[jira] [Updated] (YARN-758) Fair scheduler has some bug that causes TestRMRestart to fail

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-758: -- Attachment: yarn-758-1.patch Added a constructor to MockNM that takes vcores as well, and

[jira] [Updated] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-957: --- Attachment: YARN-957-20130731.1.patch Capacity Scheduler tries to reserve the memory more

[jira] [Commented] (YARN-758) Fair scheduler has some bug that causes TestRMRestart to fail

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

[jira] [Commented] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

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

[jira] [Created] (YARN-1006) Nodes list web page on the RM web UI is broken

Jian He created YARN-1006: - Summary: Nodes list web page on the RM web UI is broken Key: YARN-1006 URL: https://issues.apache.org/jira/browse/YARN-1006 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-76) killApplication doesn't fully kill application master on Mac OS

[ https://issues.apache.org/jira/browse/YARN-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725719#comment-13725719 ] Xuan Gong commented on YARN-76: --- [~bowang] I run the sleep task, and kill this application.

[jira] [Commented] (YARN-770) NPE NodeStatusUpdaterImpl

[ https://issues.apache.org/jira/browse/YARN-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725739#comment-13725739 ] Xuan Gong commented on YARN-770: I run several test which used a miniYarn cluster, such as

[jira] [Commented] (YARN-1001) YARN should provide per application-type and state statistics

[ https://issues.apache.org/jira/browse/YARN-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725740#comment-13725740 ] Zhijie Shen commented on YARN-1001: --- [~srimanth.gunturi], I'm not fully sure it will meet

[jira] [Commented] (YARN-990) YARN REST api needs filtering capability

[ https://issues.apache.org/jira/browse/YARN-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725748#comment-13725748 ] Zhijie Shen commented on YARN-990: -- Checked the latest trunk, RMWebServices provides the

[jira] [Updated] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not

[ https://issues.apache.org/jira/browse/YARN-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-808: --- Attachment: YARN-808.1.patch ApplicationReport does not clearly tell that the attempt is running or not

[jira] [Commented] (YARN-1001) YARN should provide per application-type and state statistics

[ https://issues.apache.org/jira/browse/YARN-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725751#comment-13725751 ] Srimanth Gunturi commented on YARN-1001: [~zjshen], yes we could filter by app-type

[jira] [Updated] (YARN-758) TestRMRestart should use MockNMs with multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-758: -- Summary: TestRMRestart should use MockNMs with multiple cores (was: Fair scheduler has some bug

[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=13725772#comment-13725772 ] Omkar Vinit Joshi commented on YARN-903: bq. NMContext is all about shared state.

[jira] [Assigned] (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:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-953: Assignee: Vinod Kumar Vavilapalli (was: Zhijie Shen) [YARN-321] Change

[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-20130731.1.patch DistributedShell throwing Errors in logs after

[jira] [Commented] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

[ https://issues.apache.org/jira/browse/YARN-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725802#comment-13725802 ] Vinod Kumar Vavilapalli commented on YARN-107: -- Clearly, we have two options,

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

[jira] [Commented] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not

[ https://issues.apache.org/jira/browse/YARN-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725809#comment-13725809 ] Hadoop QA commented on YARN-808: {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=13725818#comment-13725818 ] Zhijie Shen commented on YARN-956: -- bq. Can you also write a test for InMemory storage.

[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=13725837#comment-13725837 ] Sandy Ryza commented on YARN-972: - I should have probably tried to be more clear about what

[jira] [Commented] (YARN-758) TestRMRestart should use MockNMs with multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725842#comment-13725842 ] Sandy Ryza commented on YARN-758: - There are likely a number of other tests that have

[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=13725898#comment-13725898 ] Allen Wittenauer commented on YARN-972: --- Thought running through my head: I hope I

[jira] [Updated] (YARN-975) Adding HDFS implementation for grouped reading and writing interfaces of history storage

[ https://issues.apache.org/jira/browse/YARN-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-975: - Attachment: YARN-975.2.patch Updated the patch: 1. Fix some logic bugs in the previous patch. 2. Added

[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=13725909#comment-13725909 ] Omkar Vinit Joshi commented on YARN-573: Thanks [~jlowe] and [~sjlee0] for

[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 ] Omkar Vinit Joshi updated YARN-573: --- Attachment: YARN-573-20130731.1.patch Shared data structures in Public Localizer and

[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=13725913#comment-13725913 ] Vinod Kumar Vavilapalli commented on YARN-502: -- Though the explicit state check

[jira] [Commented] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725923#comment-13725923 ] Konstantin Boudnik commented on YARN-854: - I have started the release process...

[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-20130731.2.patch DistributedShell throwing Errors in logs after

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

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

[jira] [Updated] (YARN-758) TestRMRestart should use MockNMs with multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-758: -- Attachment: yarn-758-2.patch Updated patch to address Sandy's comment. With this fix, there was

[jira] [Updated] (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 ] Karthik Kambatla updated YARN-758: -- Summary: Augment MockNM to use multiple cores (was: TestRMRestart should use MockNMs with

[jira] [Resolved] (YARN-770) NPE NodeStatusUpdaterImpl

[ https://issues.apache.org/jira/browse/YARN-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-770. -- Resolution: Invalid [~ste...@apache.org], I am closing this as invalid for now.

[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=13725950#comment-13725950 ] Hadoop QA commented on YARN-758: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-855) YarnClient.init should ensure that yarn parameters are present

[ https://issues.apache.org/jira/browse/YARN-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725969#comment-13725969 ] Siddharth Seth commented on YARN-855: - The simplest would be to check the configuration

[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=13726039#comment-13726039 ] Xuan Gong commented on YARN-994: Yes, i will do that HeartBeat thread in

[jira] [Commented] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not

[ https://issues.apache.org/jira/browse/YARN-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726042#comment-13726042 ] Zhijie Shen commented on YARN-808: -- +1 for embedding ApplicationAttemptReport in

[jira] [Commented] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

[ https://issues.apache.org/jira/browse/YARN-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726063#comment-13726063 ] Hadoop QA commented on YARN-107: {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=13726069#comment-13726069 ] Sandy Ryza commented on YARN-758: - +1 Augment MockNM to use multiple cores

[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.2.patch Add a testcase to verify that the runtimeException will be captured and the