[
https://issues.apache.org/jira/browse/YARN-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115606#comment-14115606
]
Hitesh Shah commented on YARN-2450:
---
+1. Committing shortly.
> Fix typos in log message
[
https://issues.apache.org/jira/browse/YARN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah moved MAPREDUCE-4508 to YARN-55:
Tags: (was: YARN, NodeManager)
Component/s: (was:
[
https://issues.apache.org/jira/browse/YARN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-55:
Component/s: (was: nodemanager)
> YARN needs to properly check the NM,AM memory properties in yarn-sit
[
https://issues.apache.org/jira/browse/YARN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah moved MAPREDUCE-4578 to YARN-56:
Component/s: (was: resourcemanager)
resourcema
[
https://issues.apache.org/jira/browse/YARN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443687#comment-13443687
]
Hitesh Shah commented on YARN-55:
-
Typo in previous comment - that should have bee MAPREDUCE-
[
https://issues.apache.org/jira/browse/YARN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-10:
Attachment: YARN-10.1.patch
> dist-shell shouldn't have a (test) dependency on hadoop-mapreduce-client-cor
[
https://issues.apache.org/jira/browse/YARN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah reassigned YARN-10:
---
Assignee: Hitesh Shah
> dist-shell shouldn't have a (test) dependency on hadoop-mapreduce-client-cor
[
https://issues.apache.org/jira/browse/YARN-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah reassigned YARN-96:
---
Assignee: Hitesh Shah
> DistributedShell doesn't need to make the AMClass configurable
> ---
[
https://issues.apache.org/jira/browse/YARN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah reassigned YARN-95:
---
Assignee: Hitesh Shah
> DistributedShell throws an exception along with the help text.
> ---
[
https://issues.apache.org/jira/browse/YARN-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454366#comment-13454366
]
Hitesh Shah commented on YARN-9:
@Alejandro, given that we are designating hadoop-2.0.x as alp
[
https://issues.apache.org/jira/browse/YARN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-94:
Attachment: YARN-94.1.patch
Combined patch for YARN-94, YARN-95 and YARN-96.
> DistributedShe
[
https://issues.apache.org/jira/browse/YARN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-94:
Attachment: YARN-94.2.patch
@Vinod, makes sense. A trivial change to modify behavior to adapt to that
approac
[
https://issues.apache.org/jira/browse/YARN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455520#comment-13455520
]
Hitesh Shah commented on YARN-94:
-
@Vinod, if the patch looks fine, could you kick the pre-co
[
https://issues.apache.org/jira/browse/YARN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-56:
Summary: Handle container requests that request more resources than
currently available in the cluster (was:
[
https://issues.apache.org/jira/browse/YARN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467307#comment-13467307
]
Hitesh Shah commented on YARN-94:
-
@Vinod, could you re-check? The test I ran worked for me.
[
https://issues.apache.org/jira/browse/YARN-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-277:
-
Attachment: YARN-277.2.patch
Original changes looked fine.
However, I modified patch slightly to make cod
[
https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-193:
-
Attachment: YARN-193.4.patch
Re-based patch against latest code.
> Scheduler.normalizeReq
[
https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-193:
-
Affects Version/s: (was: 2.0.3-alpha)
2.0.2-alpha
> Scheduler.normalizeReque
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
Is
[
https://issues.apache.org/jira/browse/YARN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549133#comment-13549133
]
Hitesh Shah commented on YARN-330:
--
@Sandy, sure go ahead.
> Flakey test:
[
https://issues.apache.org/jira/browse/YARN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah reassigned YARN-330:
Assignee: Sandy Ryza
> Flakey test: TestNodeManagerShutdown#testKillContainersOnShutdown
> --
[
https://issues.apache.org/jira/browse/YARN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550465#comment-13550465
]
Hitesh Shah commented on YARN-330:
--
@Chris, yes - it is a duplicate. I guess you and @Sandy
[
https://issues.apache.org/jira/browse/YARN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550622#comment-13550622
]
Hitesh Shah commented on YARN-330:
--
@Chris, could you try the following:
on line 213 of t
[
https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551243#comment-13551243
]
Hitesh Shah commented on YARN-193:
--
@Vinod, the .4 patch was against trunk as of 8th Jan. W
[
https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-193:
-
Attachment: YARN-193.5.patch
Re-based against changes for cpu-based scheduling.
> Schedule
[
https://issues.apache.org/jira/browse/YARN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552986#comment-13552986
]
Hitesh Shah commented on YARN-330:
--
@Sandy, what do you think about the suggestion I mentio
[
https://issues.apache.org/jira/browse/YARN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553119#comment-13553119
]
Hitesh Shah commented on YARN-330:
--
+1. Latest patch looks good. Will commit in a short whi
[
https://issues.apache.org/jira/browse/YARN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-330:
-
Fix Version/s: (was: 3.0.0)
Affects Version/s: (was: 3.0.0)
> Flakey test: TestNodeMana
[
https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-193:
-
Priority: Major (was: Critical)
> Scheduler.normalizeRequest does not account for allocation requests
[
https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559140#comment-13559140
]
Hitesh Shah commented on YARN-231:
--
@Bikas, regarding the findbug warnings:
private void c
[
https://issues.apache.org/jira/browse/YARN-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559235#comment-13559235
]
Hitesh Shah commented on YARN-73:
-
Clarification for previous comment: YARN-72 only covers ki
[
https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559952#comment-13559952
]
Hitesh Shah commented on YARN-231:
--
A couple of minor comments on the fs patch:
FSRMStateS
[
https://issues.apache.org/jira/browse/YARN-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560007#comment-13560007
]
Hitesh Shah commented on YARN-277:
--
@Bikas, thanks for the patch. @Sid, thanks for the revi
[
https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560087#comment-13560087
]
Hitesh Shah commented on YARN-231:
--
@Bikas, my mistake - missed the yarn-default change. li
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
Pr
[
https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-231:
-
Summary: Add FS-based persistent store implementation for RMStateStore
(was: Add persistent store implemen
[
https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-231:
-
Description: Add stores that write RM state data to FileSystem (was: Add
stores that write RM state data
[
https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-231:
-
Description: Add store that write RM state data to FileSystem (was: Add
stores that write RM state data t
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:
[
https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560267#comment-13560267
]
Hitesh Shah commented on YARN-231:
--
FYI, filed YARN-353 for ZK based implementation.
[
https://issues.apache.org/jira/browse/YARN-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-360:
-
Assignee: Daryn Sharp
> Allow apps to concurrently register tokens for renewal
> --
Hitesh Shah created YARN-369:
Summary: Handle ( or throw a proper error when receiving) status
updates from applications that have not registered
Key: YARN-369
URL: https://issues.apache.org/jira/browse/YARN-369
[
https://issues.apache.org/jira/browse/YARN-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569270#comment-13569270
]
Hitesh Shah commented on YARN-372:
--
+1. Will commit shortly.
> Move Inline
[
https://issues.apache.org/jira/browse/YARN-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569273#comment-13569273
]
Hitesh Shah commented on YARN-372:
--
( after Jenkins +1s the patch )
> Move
[
https://issues.apache.org/jira/browse/YARN-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569659#comment-13569659
]
Hitesh Shah commented on YARN-373:
--
@Alejandro, had a few questions regarding the jira desc
[
https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah moved MAPREDUCE-4143 to YARN-378:
-
Component/s: (was: resourcemanager)
resourc
Hitesh Shah created YARN-383:
Summary: AMRMClientImpl should handle null rmClient in stop()
Key: YARN-383
URL: https://issues.apache.org/jira/browse/YARN-383
Project: Hadoop YARN
Issue Type: Bug
[
https://issues.apache.org/jira/browse/YARN-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-383:
-
Attachment: YARN-383.1.patch
Trivial patch.
> AMRMClientImpl should handle null rmClient i
[
https://issues.apache.org/jira/browse/YARN-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-383:
-
Description:
2013-02-06 09:31:33,813 INFO [Thread-2] service.CompositeService
(CompositeService.java:stop
[
https://issues.apache.org/jira/browse/YARN-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-383:
-
Attachment: YARN-383.2.patch
Updated patch with a findbugs filter.
No tests as this is a trivial fix to ch
[
https://issues.apache.org/jira/browse/YARN-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-383:
-
Attachment: YARN-383.3.patch
Fixing broken findbugs excludes for hadoop-yarn-client.
As part of the patch
[
https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574908#comment-13574908
]
Hitesh Shah commented on YARN-196:
--
Xuan, some comments:
- testNMShutdownForRegistrationF
[
https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576166#comment-13576166
]
Hitesh Shah commented on YARN-196:
--
More comments:
- Please restrict lines to 80 chars.
[
https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576194#comment-13576194
]
Hitesh Shah commented on YARN-196:
--
Sorry - ran through the patch too quickly. Xuan, please
[
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
>
[
https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-378:
-
Issue Type: Sub-task (was: Improvement)
Parent: YARN-386
> ApplicationMaster retry times shoul
[
https://issues.apache.org/jira/browse/YARN-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-337:
-
Labels: usability (was: )
> RM handles killed application tracking URL poorly
> --
[
https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-249:
-
Labels: scheduler usability web-ui (was: scheduler web-ui)
> Capacity Scheduler web page should show l
[
https://issues.apache.org/jira/browse/YARN-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-236:
-
Labels: usability (was: )
> RM should point tracking URL to RM web page when app fails to start
>
[
https://issues.apache.org/jira/browse/YARN-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-182:
-
Labels: hadoop usability (was: hadoop)
> Unnecessary "Container killed by the ApplicationMaster" messa
[
https://issues.apache.org/jira/browse/YARN-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-227:
-
Labels: usability (was: )
> Application expiration difficult to debug for end-users
>
[
https://issues.apache.org/jira/browse/YARN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-308:
-
Labels: usability (was: )
> Improve documentation about what "asks" means in AMRMProtocol
> --
[
https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-378:
-
Labels: usability (was: )
> ApplicationMaster retry times should be set by Client
> --
Hitesh Shah created YARN-405:
Summary: Add command start-up time to environment of a container
to track launch costs
Key: YARN-405
URL: https://issues.apache.org/jira/browse/YARN-405
Project: Hadoop YARN
Hitesh Shah created YARN-406:
Summary: TestRackResolver fails when local network resolves
"host1" to a valid host
Key: YARN-406
URL: https://issues.apache.org/jira/browse/YARN-406
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-406:
-
Attachment: YARN-406.1.patch
> TestRackResolver fails when local network resolves "host1" to a valid ho
[
https://issues.apache.org/jira/browse/YARN-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-405:
-
Attachment: YARN-405.1.patch
> Add command start-up time to environment of a container to track launch
[
https://issues.apache.org/jira/browse/YARN-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-405:
-
Description: For applications like MapReduce, jvm launch cost has always
been considered a factor in perfor
[
https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579475#comment-13579475
]
Hitesh Shah commented on YARN-196:
--
Fix trailing space issues in the patch. There also seem
[
https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579641#comment-13579641
]
Hitesh Shah commented on YARN-196:
--
@Xuan, the comment about the RM dying was for a later p
[
https://issues.apache.org/jira/browse/YARN-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581515#comment-13581515
]
Hitesh Shah commented on YARN-407:
--
@Zhijie, does this seem like a dup of YARN-193?
[
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 exa
[
https://issues.apache.org/jira/browse/YARN-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-100:
-
Labels: usability (was: )
> container-executor should deal with stdout, stderr better
> --
[
https://issues.apache.org/jira/browse/YARN-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-100:
-
Labels: (was: usability)
> container-executor should deal with stdout, stderr better
> --
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
Repor
[
https://issues.apache.org/jira/browse/YARN-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-404:
-
Priority: Blocker (was: Critical)
> Node Manager leaks Data Node connections
> ---
[
https://issues.apache.org/jira/browse/YARN-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-386:
-
Priority: Blocker (was: Major)
> [Umbrella] YARN API cleanup
> ---
>
>
[
https://issues.apache.org/jira/browse/YARN-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-397:
-
Priority: Blocker (was: Major)
> RM Scheduler api enhancements
> -
>
>
[
https://issues.apache.org/jira/browse/YARN-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-270:
-
Priority: Blocker (was: Major)
> RM scheduler event handler thread gets behind
> -
[
https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-41:
Priority: Blocker (was: Major)
> The RM should handle the graceful shutdown of the NM.
>
[
https://issues.apache.org/jira/browse/YARN-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-142:
-
Priority: Blocker (was: Critical)
> Change YARN APIs to throw IOException
> --
[
https://issues.apache.org/jira/browse/YARN-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-69:
Priority: Blocker (was: Major)
> RM should throw different exceptions for while querying app/node/queue
>
[
https://issues.apache.org/jira/browse/YARN-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-85:
Priority: Critical (was: Major)
> Allow per job log aggregation configuration
> -
[
https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-117:
-
Priority: Blocker (was: Major)
> Enhance YARN service model
> --
>
>
[
https://issues.apache.org/jira/browse/YARN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-99:
Priority: Blocker (was: Major)
> Jobs fail during resource localization when directories in file cache re
[
https://issues.apache.org/jira/browse/YARN-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-34:
Priority: Blocker (was: Major)
> Split/Cleanup YARN and MAPREDUCE documentation
> ---
[
https://issues.apache.org/jira/browse/YARN-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-396:
-
Priority: Blocker (was: Major)
> Rationalize AllocateResponse in RM scheduler API
> --
[
https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-387:
-
Priority: Blocker (was: Major)
> Fix inconsistent protocol naming
>
>
[
https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-378:
-
Priority: Major (was: Minor)
> ApplicationMaster retry times should be set by Client
> ---
[
https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-71:
Issue Type: Bug (was: Test)
> Ensure/confirm that the NodeManager cleanup their local filesystem when the
[
https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-71:
Priority: Critical (was: Major)
> Ensure/confirm that the NodeManager cleanup their local filesystem when
[
https://issues.apache.org/jira/browse/YARN-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-226:
-
Priority: Blocker (was: Major)
> Log aggregation should not assume an AppMaster will have containerId
[
https://issues.apache.org/jira/browse/YARN-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated YARN-47:
Priority: Blocker (was: Major)
> Security issues in YARN
>
>
>
[
https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583823#comment-13583823
]
Hitesh Shah commented on YARN-196:
--
Patch still has trailing whitespace issues.
In YarnCon
[
https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584366#comment-13584366
]
Hitesh Shah commented on YARN-193:
--
@Zhijie, distributedshell is an example application and
[
https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588694#comment-13588694
]
Hitesh Shah commented on YARN-196:
--
+ public static final int DEFAULT_RESOURCEMANAGER_CONN
[
https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588696#comment-13588696
]
Hitesh Shah commented on YARN-196:
--
Also, description in yarn-default.xml should mention th
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
Issue
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: Bug
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 Y
301 - 400 of 670 matches
Mail list logo
