[jira] [Created] (YARN-5219) When an export var command fails in launch_container.sh, the full container launch should fail

Hitesh Shah created YARN-5219: - Summary: When an export var command fails in launch_container.sh, the full container launch should fail Key: YARN-5219 URL: https://issues.apache.org/jira/browse/YARN-5219

Re: [DISCUSS] Treating LimitedPrivate({"MapReduce"}) as Public APIs for YARN applications

te: > > >> On May 10, 2016, at 8:37 AM, Hitesh Shah <hit...@apache.org> wrote: >> >> There have been various discussions on various JIRAs where upstream projects >> such as YARN apps ( Tez, Slider, etc ) are called out for using the above >> so-called P

[jira] [Created] (YARN-4990) Re-direction of a particular log file within in a container in NM UI does not redirect properly to Log Server ( history ) on container completion

Hitesh Shah created YARN-4990: - Summary: Re-direction of a particular log file within in a container in NM UI does not redirect properly to Log Server ( history ) on container completion Key: YARN-4990 URL: https

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

+1 (binding) Did the basic checks and ran against a single node local setup. — Hitesh On Jan 14, 2016, at 8:57 PM, Vinod Kumar Vavilapalli wrote: > Hi all, > > I've created an updated release candidate RC2 for Apache Hadoop 2.7.2. > > As discussed before, this is the

Re: Planning Hadoop 2.6.1 release

Jason Lowe just filed YARN-4047 ( patch available too ) which probably is also a good candidate for 2.6.1 or 2.6.2 if the list is frozen. I have labelled the jira as a 2.6.1 candidate. Feel free to switch to 2.6.2 if needed. thanks — Hitesh On Aug 10, 2015, at 4:15 PM, Vinod Kumar Vavilapalli

Re: YARN replica selection

Moving conversation to yarn-dev. BCC’ed hdfs-dev. YARN actually does not do anything except give back containers based on what an application requested for. It is up to each and every application to first figure out where the data is located and then make optimal choices based on which node to

[jira] [Resolved] (YARN-2916) MiniYARNCluster should support enabling Timeline and new services via config

[ https://issues.apache.org/jira/browse/YARN-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-2916. --- Resolution: Duplicate MiniYARNCluster should support enabling Timeline and new services via config

[jira] [Resolved] (YARN-900) YarnClientApplication uses composition to hold GetNewApplicationResponse instead of having a simpler flattened structure

[ https://issues.apache.org/jira/browse/YARN-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-900. -- Resolution: Not A Problem YarnClientApplication uses composition to hold GetNewApplicationResponse

[jira] [Resolved] (YARN-971) hadoop-yarn-api pom does not define a dependencies tag

[ https://issues.apache.org/jira/browse/YARN-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-971. -- Resolution: Duplicate hadoop-yarn-api pom does not define a dependencies tag

[jira] [Resolved] (YARN-2840) Timeline should support creation of Domains where domainId is not provided by the user

[ https://issues.apache.org/jira/browse/YARN-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-2840. --- Resolution: Won't Fix Timeline should support creation of Domains where domainId is not provided

[jira] [Resolved] (YARN-2833) Timeline Domains should be immutable by default

[ https://issues.apache.org/jira/browse/YARN-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-2833. --- Resolution: Won't Fix Timeline Domains should be immutable by default

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

There are a couple of different approaches we could take. How about publishing/releasing bits such as “2.8.0-RC0”. Downstream projects can depend on these and use them normally similar to the approach that they would have taken with release 2.8.0 or 2.8.0-alpha. After some baking ( or more RC

[jira] [Created] (YARN-3544) AM logs link missing in the RM UI for a completed app

Hitesh Shah created YARN-3544: - Summary: AM logs link missing in the RM UI for a completed app Key: YARN-3544 URL: https://issues.apache.org/jira/browse/YARN-3544 Project: Hadoop YARN Issue

[jira] [Created] (YARN-3296) yarn.nodemanager.container-monitor.process-tree.class is configurable but ResourceCalculatorProcessTree class is marked Private

Hitesh Shah created YARN-3296: - Summary: yarn.nodemanager.container-monitor.process-tree.class is configurable but ResourceCalculatorProcessTree class is marked Private Key: YARN-3296 URL: https://issues.apache.org

[jira] [Created] (YARN-3297) Changes for ResourceCalculatorProcessTree in YARN-3122 could be done in a more compatible manner

Hitesh Shah created YARN-3297: - Summary: Changes for ResourceCalculatorProcessTree in YARN-3122 could be done in a more compatible manner Key: YARN-3297 URL: https://issues.apache.org/jira/browse/YARN-3297

[jira] [Created] (YARN-3239) WebAppProxy does not support a final tracking url which has query fragments and params

Hitesh Shah created YARN-3239: - Summary: WebAppProxy does not support a final tracking url which has query fragments and params Key: YARN-3239 URL: https://issues.apache.org/jira/browse/YARN-3239

[jira] [Created] (YARN-3197) Confusing log generated by CapacityScheduler

Hitesh Shah created YARN-3197: - Summary: Confusing log generated by CapacityScheduler Key: YARN-3197 URL: https://issues.apache.org/jira/browse/YARN-3197 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-2976) Invalid docs for specifying yarn.nodemanager.docker-container-executor.exec-name

Hitesh Shah created YARN-2976: - Summary: Invalid docs for specifying yarn.nodemanager.docker-container-executor.exec-name Key: YARN-2976 URL: https://issues.apache.org/jira/browse/YARN-2976 Project

[jira] [Resolved] (YARN-405) Add command start-up time to environment of a container to track launch costs

[ https://issues.apache.org/jira/browse/YARN-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-405. -- Resolution: Not a Problem Add command start-up time to environment of a container to track launch costs

Re: [VOTE] Release Apache Hadoop 2.6.0

+1 (binding) Built Hadoop from source, compiled Tez against the hadoop jars pushed to staging repo and ran a few example Tez jobs on a single node cluster. — HItesh On Nov 13, 2014, at 3:08 PM, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created another release candidate

[jira] [Created] (YARN-2859) ApplicationHistoryServer binds to default port 8188 in MiniYARNCluster

Hitesh Shah created YARN-2859: - Summary: ApplicationHistoryServer binds to default port 8188 in MiniYARNCluster Key: YARN-2859 URL: https://issues.apache.org/jira/browse/YARN-2859 Project: Hadoop YARN

[jira] [Created] (YARN-2860) MiniTezCluster needs to be cleaned up to remove MR dependencies

Hitesh Shah created YARN-2860: - Summary: MiniTezCluster needs to be cleaned up to remove MR dependencies Key: YARN-2860 URL: https://issues.apache.org/jira/browse/YARN-2860 Project: Hadoop YARN

[jira] [Created] (YARN-2840) Timeline should support creation of Domains where domainId is not provided by the user

Hitesh Shah created YARN-2840: - Summary: Timeline should support creation of Domains where domainId is not provided by the user Key: YARN-2840 URL: https://issues.apache.org/jira/browse/YARN-2840 Project

[jira] [Created] (YARN-2835) YARN WebApps should be a public API

Hitesh Shah created YARN-2835: - Summary: YARN WebApps should be a public API Key: YARN-2835 URL: https://issues.apache.org/jira/browse/YARN-2835 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-2833) Timeline Domains should be immutable by default

Hitesh Shah created YARN-2833: - Summary: Timeline Domains should be immutable by default Key: YARN-2833 URL: https://issues.apache.org/jira/browse/YARN-2833 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-2660) Tarball as local resource type archive fails to localize on Windows

Hitesh Shah created YARN-2660: - Summary: Tarball as local resource type archive fails to localize on Windows Key: YARN-2660 URL: https://issues.apache.org/jira/browse/YARN-2660 Project: Hadoop YARN

Re: [VOTE] Migration from subversion to git for version control

+1 — Hitesh On Aug 8, 2014, at 7:57 PM, Karthik Kambatla ka...@cloudera.com wrote: I have put together this proposal based on recent discussion on this topic. Please vote on the proposal. The vote runs for 7 days. 1. Migrate from subversion to git for version control. 2.

Re: crossPlatformifyMREnv exception

Hi Robert, If you look at the tez jars, you will probably see a couple of mapreduce jars that Tez depends on under TEZ_BASE_DIR/lib/. Are these jars inconsistent with respect to the version of hadoop/mapreduce on the cluster? — Hitesh On Jun 19, 2014, at 2:59 PM, Grandl Robert

Re: crossPlatformifyMREnv exception

, but I am still not able to run correctly hive queries over tez or mapreduce. I already spent way too much time with this stuff and still is not running properly. Do you have any other suggestions, what to try ? On Thursday, June 19, 2014 4:30 PM, Hitesh Shah hit...@apache.org

[jira] [Created] (YARN-2092) Incompatible org.codehaus.jackson* dependencies when moving from 2.4.0 to 2.5.0-SNAPSHOT

Hitesh Shah created YARN-2092: - Summary: Incompatible org.codehaus.jackson* dependencies when moving from 2.4.0 to 2.5.0-SNAPSHOT Key: YARN-2092 URL: https://issues.apache.org/jira/browse/YARN-2092

[jira] [Created] (YARN-1915) ClientToAMTokenMasterKey should be provided to AM at launch time

Hitesh Shah created YARN-1915: - Summary: ClientToAMTokenMasterKey should be provided to AM at launch time Key: YARN-1915 URL: https://issues.apache.org/jira/browse/YARN-1915 Project: Hadoop YARN

Re: About Map 100% reduce %0 issue

You are missing the following in your yarn site: property nameyarn.nodemanager.aux-services.mapreduce_shuffle.class/name valueorg.apache.hadoop.mapred.ShuffleHandler/value /property You will need to restart the nodemanager for this property to take effect. -- Hitesh On Mar

[jira] [Created] (YARN-1768) yarn kill non-existent application is too verbose

Hitesh Shah created YARN-1768: - Summary: yarn kill non-existent application is too verbose Key: YARN-1768 URL: https://issues.apache.org/jira/browse/YARN-1768 Project: Hadoop YARN Issue Type

[jira] [Created] (YARN-1759) Configuration settings can potentially disappear post YARN-1666

Hitesh Shah created YARN-1759: - Summary: Configuration settings can potentially disappear post YARN-1666 Key: YARN-1759 URL: https://issues.apache.org/jira/browse/YARN-1759 Project: Hadoop YARN

[jira] [Created] (YARN-1758) MiniYARNCluster broken post YARN-1666

Hitesh Shah created YARN-1758: - Summary: MiniYARNCluster broken post YARN-1666 Key: YARN-1758 URL: https://issues.apache.org/jira/browse/YARN-1758 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-1626) Allow logs to be pulled for a given containerId without specifying nodeAddress

Hitesh Shah created YARN-1626: - Summary: Allow logs to be pulled for a given containerId without specifying nodeAddress Key: YARN-1626 URL: https://issues.apache.org/jira/browse/YARN-1626 Project: Hadoop

[jira] [Resolved] (YARN-1457) YARN single node install issues on mvn clean install assembly:assembly on mapreduce project

[ https://issues.apache.org/jira/browse/YARN-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-1457. --- Resolution: Invalid Native builds are only supported on Linux. For Mac, -Pnative is not supported

[jira] [Created] (YARN-1273) Distributed shell does not account for start container failures reported asynchronously.

Hitesh Shah created YARN-1273: - Summary: Distributed shell does not account for start container failures reported asynchronously. Key: YARN-1273 URL: https://issues.apache.org/jira/browse/YARN-1273

[jira] [Created] (YARN-1238) Fix use of Shuffle service after changes in YARN/MR due to YARN-1229

Hitesh Shah created YARN-1238: - Summary: Fix use of Shuffle service after changes in YARN/MR due to YARN-1229 Key: YARN-1238 URL: https://issues.apache.org/jira/browse/YARN-1238 Project: Hadoop YARN

Re: Node scheduling in 2.1.x

Have you taken a look at https://issues.apache.org/jira/browse/YARN-326 ? -- Hitesh On Sep 6, 2013, at 11:02 AM, hilfi alkaff wrote: Thanks for all the replies. I think I have found the relevant codes that I would like to modify. That said, a project that I'm doing now requires containers

Re: Node scheduling in 2.1.x

it was done in 2.0.X. You needed to do request for node/rack/* and if you got lucky you got the node you wanted. Do you still need to allocate host for node/rack/* or is plain host just fine? Will strict locality also work for allocation for just racks? On Fri, Sep 6, 2013 at 7:52 PM, Hitesh

[jira] [Created] (YARN-1070) ContainerImpl State Machine: Invalid event: CONTAINER_KILLED_ON_REQUEST at CONTAINER_CLEANEDUP_AFTER_KILL

Hitesh Shah created YARN-1070: - Summary: ContainerImpl State Machine: Invalid event: CONTAINER_KILLED_ON_REQUEST at CONTAINER_CLEANEDUP_AFTER_KILL Key: YARN-1070 URL: https://issues.apache.org/jira/browse/YARN-1070

[jira] [Created] (YARN-1037) Create a helper function to create a local resource object given a path to file

Hitesh Shah created YARN-1037: - Summary: Create a helper function to create a local resource object given a path to file Key: YARN-1037 URL: https://issues.apache.org/jira/browse/YARN-1037 Project

[jira] [Created] (YARN-971) hadoop-yarn-api pom does not define a dependencies tag

Hitesh Shah created YARN-971: Summary: hadoop-yarn-api pom does not define a dependencies tag Key: YARN-971 URL: https://issues.apache.org/jira/browse/YARN-971 Project: Hadoop YARN Issue Type

[jira] [Created] (YARN-931) Overlapping classes across hadoop-yarn-api and hadoop-yarn-common

Hitesh Shah created YARN-931: Summary: Overlapping classes across hadoop-yarn-api and hadoop-yarn-common Key: YARN-931 URL: https://issues.apache.org/jira/browse/YARN-931 Project: Hadoop YARN

Re: [VOTE] Release Apache Hadoop 2.1.0-beta

Hi Arun, From a YARN perspective, YARN-791 and YARN-727 are 2 jiras that may potentially change the apis. They can implemented in a backward compat fashion if committed after 2.1.0. However, this will require adding of differently-named apis ( different urls in case of the webservices ) and

[jira] [Created] (YARN-868) YarnClient should set the service address in tokens returned by getRMDelegationToken()

Hitesh Shah created YARN-868: Summary: YarnClient should set the service address in tokens returned by getRMDelegationToken() Key: YARN-868 URL: https://issues.apache.org/jira/browse/YARN-868 Project

[jira] [Created] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

Hitesh Shah created YARN-848: Summary: Nodemanager does not register with RM using the fully qualified hostname Key: YARN-848 URL: https://issues.apache.org/jira/browse/YARN-848 Project: Hadoop YARN

[jira] [Created] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

Hitesh Shah created YARN-814: Summary: Difficult to diagnose a failed container launch when error due to invalid environment variable Key: YARN-814 URL: https://issues.apache.org/jira/browse/YARN-814

[jira] [Created] (YARN-778) Failures in container launches due to issues like disk failure are difficult to diagnose

Hitesh Shah created YARN-778: Summary: Failures in container launches due to issues like disk failure are difficult to diagnose Key: YARN-778 URL: https://issues.apache.org/jira/browse/YARN-778 Project

[jira] [Resolved] (YARN-778) Failures in container launches due to issues like disk failure are difficult to diagnose

[ https://issues.apache.org/jira/browse/YARN-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-778. -- Resolution: Duplicate Failures in container launches due to issues like disk failure are difficult

Re: [VOTE] Release Apache Hadoop 0.23.8

+1 (non-binding) Built from source, ran some basic tests on a single node cluster. -- Hitesh On May 28, 2013, at 9:00 AM, Thomas Graves wrote: I've created a release candidate (RC0) for hadoop-0.23.8 that I would like to release. This release is a sustaining release with several

[jira] [Created] (YARN-734) Error in ContainerLaunchContextPBImpl when trying to launch a container

Hitesh Shah created YARN-734: Summary: Error in ContainerLaunchContextPBImpl when trying to launch a container Key: YARN-734 URL: https://issues.apache.org/jira/browse/YARN-734 Project: Hadoop YARN

[jira] [Resolved] (YARN-734) Error in ContainerLaunchContextPBImpl when trying to launch a container

[ https://issues.apache.org/jira/browse/YARN-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-734. -- Resolution: Invalid Error in ContainerLaunchContextPBImpl when trying to launch a container

Re: Custom ApplicationMaster development

be written by iterative MapReduce jobs, but which can potentially be much more efficient if they are able to avoid landing intermediate results on HDFS. Thanks John -Original Message- From: Hitesh Shah [mailto:hit...@hortonworks.com] Sent: Thursday, May 23, 2013 5:10 PM To: yarn

Re: Custom ApplicationMaster development

Hello John To add to Chris' email: Do take a look at http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/WritingYarnApplications.html - this is probably a bit of date. - the actual source code of distributed-shell in the source tree would be the best guideline to follow

[jira] [Created] (YARN-605) Failing unit test in TestNMWebServices when using git for source control

Hitesh Shah created YARN-605: Summary: Failing unit test in TestNMWebServices when using git for source control Key: YARN-605 URL: https://issues.apache.org/jira/browse/YARN-605 Project: Hadoop YARN

Re: container memory resource request

As some folks have mentioned earlier, it is very likely that yarn.scheduler.minimum-allocation-mb is set to 2048 in yarn-site.xml. If this is set to something different, it might be helpful to provide what version of hadoop you are running as well as a copy of your yarn-site.xml from the node

[jira] [Created] (YARN-576) RM should not allow registrations from NMs that do not satisfy minimum scheduler allocations

Hitesh Shah created YARN-576: Summary: RM should not allow registrations from NMs that do not satisfy minimum scheduler allocations Key: YARN-576 URL: https://issues.apache.org/jira/browse/YARN-576

[jira] [Created] (YARN-571) User should not be part of ContainerLaunchContext

Hitesh Shah created YARN-571: Summary: User should not be part of ContainerLaunchContext Key: YARN-571 URL: https://issues.apache.org/jira/browse/YARN-571 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-572) Remove duplication of data in Container

Hitesh Shah created YARN-572: Summary: Remove duplication of data in Container Key: YARN-572 URL: https://issues.apache.org/jira/browse/YARN-572 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-550) ContainerLaunchContext::getServiceData and setServiceData need a lot of clarification

Hitesh Shah created YARN-550: Summary: ContainerLaunchContext::getServiceData and setServiceData need a lot of clarification Key: YARN-550 URL: https://issues.apache.org/jira/browse/YARN-550 Project

Re: Failed: YARN-412 PreCommit Build #638

Hello Roger, Please take a look at https://builds.apache.org/job/PreCommit-YARN-Build/638/artifact/trunk/patchprocess/patchJavacWarnings.txt It shows a compile time failure. I have added details to the jira. -- Hitesh On Apr 1, 2013, at 1:07 PM, Roger Hoover wrote: Hi, Any ideas

[jira] [Created] (YARN-510) Writing Yarn Applications documentation should be changed to signify use of of fully qualified paths when localizing resources

Hitesh Shah created YARN-510: Summary: Writing Yarn Applications documentation should be changed to signify use of of fully qualified paths when localizing resources Key: YARN-510 URL: https://issues.apache.org/jira

[jira] [Created] (YARN-497) yarn unmanaged-am launcher jar does not define a main class in its manifest

Hitesh Shah created YARN-497: Summary: yarn unmanaged-am launcher jar does not define a main class in its manifest Key: YARN-497 URL: https://issues.apache.org/jira/browse/YARN-497 Project: Hadoop YARN

[jira] [Created] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats

Hitesh Shah created YARN-479: Summary: NM retry behavior for connection to RM should be similar for lost heartbeats Key: YARN-479 URL: https://issues.apache.org/jira/browse/YARN-479 Project: Hadoop YARN

[jira] [Created] (YARN-475) Remove ApplicationConstants.AM_APP_ATTEMPT_ID_ENV as it is no longer set in an AM's environment

Hitesh Shah created YARN-475: Summary: Remove ApplicationConstants.AM_APP_ATTEMPT_ID_ENV as it is no longer set in an AM's environment Key: YARN-475 URL: https://issues.apache.org/jira/browse/YARN-475

[jira] [Created] (YARN-470) Support a way to disable resource monitoring on the NodeManager

Hitesh Shah created YARN-470: Summary: Support a way to disable resource monitoring on the NodeManager Key: YARN-470 URL: https://issues.apache.org/jira/browse/YARN-470 Project: Hadoop YARN

[jira] [Created] (YARN-471) RM does not validate the resource capability of an NM when the NM registers with the RM

Hitesh Shah created YARN-471: Summary: RM does not validate the resource capability of an NM when the NM registers with the RM Key: YARN-471 URL: https://issues.apache.org/jira/browse/YARN-471 Project

[jira] [Created] (YARN-435) Make it easier to access cluster topology information in an AM

Hitesh Shah created YARN-435: Summary: Make it easier to access cluster topology information in an AM Key: YARN-435 URL: https://issues.apache.org/jira/browse/YARN-435 Project: Hadoop YARN

[jira] [Created] (YARN-436) Document how to use DistributedShell yarn application

Hitesh Shah created YARN-436: Summary: Document how to use DistributedShell yarn application Key: YARN-436 URL: https://issues.apache.org/jira/browse/YARN-436 Project: Hadoop YARN Issue Type

[jira] [Created] (YARN-437) Update documentation of Writing Yarn applications to match current best practices

Hitesh Shah created YARN-437: Summary: Update documentation of Writing Yarn applications to match current best practices Key: YARN-437 URL: https://issues.apache.org/jira/browse/YARN-437 Project: Hadoop

[jira] [Created] (YARN-414) [Umbrella] Usability issues in YARN

Hitesh Shah created YARN-414: Summary: [Umbrella] Usability issues in YARN Key: YARN-414 URL: https://issues.apache.org/jira/browse/YARN-414 Project: Hadoop YARN Issue Type: Bug

[jira] [Resolved] (YARN-130) Yarn examples use wrong configuration

[ https://issues.apache.org/jira/browse/YARN-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-130. -- Resolution: Fixed Closing this out as this was addressed as part of YARN-277. Yarn

[jira] [Resolved] (YARN-195) AM should have a way of telling RM to not allocate containers on some nodes

[ https://issues.apache.org/jira/browse/YARN-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-195. -- Resolution: Duplicate AM should have a way of telling RM to not allocate containers on some nodes

[jira] [Created] (YARN-352) Inconsistent picture of how a container was killed when querying RM and NM in case of preemption

Hitesh Shah created YARN-352: Summary: Inconsistent picture of how a container was killed when querying RM and NM in case of preemption Key: YARN-352 URL: https://issues.apache.org/jira/browse/YARN-352

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

Hitesh Shah created YARN-353: Summary: Add Zookeeper-based store implementation for RMStateStore Key: YARN-353 URL: https://issues.apache.org/jira/browse/YARN-353 Project: Hadoop YARN Issue Type

[jira] [Created] (YARN-330) Flakey test: TestNodeManagerShutdown#testKillContainersOnShutdown

Hitesh Shah created YARN-330: Summary: Flakey test: TestNodeManagerShutdown#testKillContainersOnShutdown Key: YARN-330 URL: https://issues.apache.org/jira/browse/YARN-330 Project: Hadoop YARN