[
https://issues.apache.org/jira/browse/YARN-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned YARN-511:
Assignee: (was: Harsh J)
> ConverterUtils's getPathFromYarnURL and getYarnUrlFromPath work with fully
>
[
https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180718#comment-15180718
]
Harsh J commented on YARN-4767:
---
One add-on note that we can likely also address with this on
[
https://issues.apache.org/jira/browse/YARN-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J moved MAPREDUCE-2745 to YARN-3376:
--
Component/s: (was: mrv2)
nodemanager
Affects
[
https://issues.apache.org/jira/browse/YARN-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377378#comment-14377378
]
Harsh J commented on YARN-1880:
---
+1, this still applies. Committing shortly, thanks [~ozawa]
[
https://issues.apache.org/jira/browse/YARN-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-1880:
--
Affects Version/s: 2.6.0
> Cleanup TestApplicationClientProtocolOnHA
> -
[
https://issues.apache.org/jira/browse/YARN-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-1880:
--
Component/s: test
> Cleanup TestApplicationClientProtocolOnHA
> -
>
>
[
https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482505#comment-14482505
]
Harsh J commented on YARN-2424:
---
[~sidharta-s] - Yes, it appears the warning was skipped in t
[
https://issues.apache.org/jira/browse/YARN-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-3462:
--
Target Version/s: 2.8.0, 2.7.1
Hadoop Flags: Reviewed
Thanks [~Naganarasimha], lgtm, +1. Committing short
[
https://issues.apache.org/jira/browse/YARN-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708940#comment-14708940
]
Harsh J commented on YARN-4065:
---
Agreed - and figuring this has wasted a few mins at another
[
https://issues.apache.org/jira/browse/YARN-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned YARN-4065:
-
Assignee: Casey Brotherton
> container-executor error should include effective user id
> -
[
https://issues.apache.org/jira/browse/YARN-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-4222:
--
Target Version/s: 2.8.0
> Retries is typoed to spell Retires in parts of hadoop-yarn and hadoop-common
>
[
https://issues.apache.org/jira/browse/YARN-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-4222:
--
Fix Version/s: (was: 2.8.0)
> Retries is typoed to spell Retires in parts of hadoop-yarn and hadoop-common
>
[
https://issues.apache.org/jira/browse/YARN-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942274#comment-14942274
]
Harsh J commented on YARN-4222:
---
Failed tests aren't related. Thanks for the changes!
+1, co
[
https://issues.apache.org/jira/browse/YARN-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966500#comment-14966500
]
Harsh J commented on YARN-4263:
---
Thank you for the fix and tests! Some comments:
- Could you
Harsh J created YARN-2760:
-
Summary: Completely remove word 'experimental' from FairScheduler
docs
Key: YARN-2760
URL: https://issues.apache.org/jira/browse/YARN-2760
Project: Hadoop YARN
Issue Type
[
https://issues.apache.org/jira/browse/YARN-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-2760:
--
Attachment: YARN-2760.patch
> Completely remove word 'experimental' from FairScheduler docs
> ---
[
https://issues.apache.org/jira/browse/YARN-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186325#comment-14186325
]
Harsh J commented on YARN-2760:
---
Patch can certainly be applied. Script or build box is havin
[
https://issues.apache.org/jira/browse/YARN-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-2760:
--
Attachment: YARN-2760.patch
Re-uploading patch to retry after the patching issue was fixed in buildbot.
> Comple
[
https://issues.apache.org/jira/browse/YARN-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214806#comment-14214806
]
Harsh J commented on YARN-2578:
---
bq. We never implemented health monitoring like in ZKFC with
[
https://issues.apache.org/jira/browse/YARN-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned YARN-2891:
-
Assignee: Dustin Cote
Assigning to Dustin as he mentioned offline that he'd like to contribute on
this.
[
https://issues.apache.org/jira/browse/YARN-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-2891:
--
Hadoop Flags: Reviewed
> Failed Container Executor does not provide a clear error message
> -
[
https://issues.apache.org/jira/browse/YARN-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned YARN-1918:
-
Assignee: Anandha L Ranganathan
> Typo in description and error message for 'yarn.resourcemanager.cluster-
[
https://issues.apache.org/jira/browse/YARN-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned YARN-281:
Assignee: Wangda Tan (was: Harsh J)
Sorry on delay, reassigned.
> Add a test for YARN Schedulers' MAXIMUM_A
[
https://issues.apache.org/jira/browse/YARN-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned YARN-349:
Assignee: (was: Harsh J)
> Send out last-minute load averages in TaskTrackerStatus
>
[
https://issues.apache.org/jira/browse/YARN-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242829#comment-14242829
]
Harsh J commented on YARN-2950:
---
File of message is
{{hadoop-yarn-project/hadoop-yarn/hadoop
Harsh J created YARN-2950:
-
Summary: Change message to mandate, not suggest JS requirement on
UI
Key: YARN-2950
URL: https://issues.apache.org/jira/browse/YARN-2950
Project: Hadoop YARN
Issue Type:
[
https://issues.apache.org/jira/browse/YARN-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-2950:
--
Labels: newbie (was: )
> Change message to mandate, not suggest JS requirement on UI
> -
[
https://issues.apache.org/jira/browse/YARN-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-2950:
--
Affects Version/s: 2.5.0
> Change message to mandate, not suggest JS requirement on UI
>
[
https://issues.apache.org/jira/browse/YARN-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-2950:
--
Attachment: YARN-2950-2.patch
Thanks Dustin!
Looks good to me. I've gone ahead and made a small change to keep t
[
https://issues.apache.org/jira/browse/YARN-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-2999:
--
Labels: jdk7 (was: )
> Compilation error in AllocationConfiguration.java in java1.7 while running
> tests
> ---
Harsh J created YARN-3021:
-
Summary: YARN's delegation-token handling disallows certain trust
setups to operate properly
Key: YARN-3021
URL: https://issues.apache.org/jira/browse/YARN-3021
Project: Hadoop YAR
[
https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-3021:
--
Attachment: YARN-3021.patch
A patch that illustrates the change.
> YARN's delegation-token handling disallows ce
[
https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298513#comment-14298513
]
Harsh J commented on YARN-3021:
---
Overall the patch looks fine to me, but please do hold up fo
[
https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310570#comment-14310570
]
Harsh J commented on YARN-3021:
---
[~vinodkv],
Many thanks for the response here!
bq. Though
[
https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-3021:
--
Summary: YARN's delegation-token handling disallows certain trust setups to
operate properly over DistCp (was: Y
[
https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313593#comment-14313593
]
Harsh J commented on YARN-3021:
---
Thanks again [~vinodkv] and [~yzhangal],
bq. bq. RM can sim
[
https://issues.apache.org/jira/browse/YARN-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved YARN-1487.
---
Resolution: Invalid
The plugin effort has moved out of Apache Hadoop into its own Apache
(incubator) project
[
https://issues.apache.org/jira/browse/YARN-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved YARN-1486.
---
Resolution: Invalid
Resolving as Invalid. Please see my comment on YARN-1487 on why.
> How to develop an appl
[
https://issues.apache.org/jira/browse/YARN-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451772#comment-13451772
]
Harsh J commented on YARN-80:
-
Hi Arun,
Thanks very much for doing this! We could probably addre
[
https://issues.apache.org/jira/browse/YARN-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459016#comment-13459016
]
Harsh J commented on YARN-111:
--
Robert,
I still see Job priority exist in MR1 (1.x). Which JIR
[
https://issues.apache.org/jira/browse/YARN-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459567#comment-13459567
]
Harsh J commented on YARN-111:
--
bq. So application's priority doesn't take effect.Am i right?
[
https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461314#comment-13461314
]
Harsh J commented on YARN-20:
-
[~nemon] - Please do submit a patch annotating in the default XML
[
https://issues.apache.org/jira/browse/YARN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-101:
-
Description:
see the red color:
org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.java
protected v
[
https://issues.apache.org/jira/browse/YARN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461315#comment-13461315
]
Harsh J commented on YARN-101:
--
[~xieguiming] - I tweaked the sentences a bit so you're soundin
[
https://issues.apache.org/jira/browse/YARN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461316#comment-13461316
]
Harsh J commented on YARN-56:
-
bq. Handle container requests that request more resources than ava
[
https://issues.apache.org/jira/browse/YARN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461317#comment-13461317
]
Harsh J commented on YARN-56:
-
+1 on Robert's timeout suggestion though (per app, with a reasonab
[
https://issues.apache.org/jira/browse/YARN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461318#comment-13461318
]
Harsh J commented on YARN-115:
--
Do we even need these specific specifiers? Most users have been
[
https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-71:
Issue Type: Test (was: Bug)
> Ensure/confirm that the NodeManager cleanup their local filesystem when they
> res
[
https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-71:
Labels: (was: test)
> Ensure/confirm that the NodeManager cleanup their local filesystem when they
> restart
>
[
https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-71:
Labels: test (was: )
> Ensure/confirm that the NodeManager cleanup their local filesystem when they
> restart
>
[
https://issues.apache.org/jira/browse/YARN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J moved HADOOP-8351 to YARN-116:
--
Component/s: (was: util)
nodemanager
Affects Version/
[
https://issues.apache.org/jira/browse/YARN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-116:
-
Environment: (was: suse)
> Add exclude/include file , need restart NN or RM.
>
[
https://issues.apache.org/jira/browse/YARN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-116:
-
Component/s: (was: nodemanager)
resourcemanager
> Add exclude/include file , need restart
[
https://issues.apache.org/jira/browse/YARN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-116:
-
Summary: RM is missing ability to add include/exclude files without a
restart (was: Add exclude/include file , nee
[
https://issues.apache.org/jira/browse/YARN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-116:
-
Description:
The "yarn.resourcemanager.nodes.include-path" default value is "", if we need
to add an include file,
[
https://issues.apache.org/jira/browse/YARN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-116:
-
Attachment: YARN-116.patch
Cleaned up Xie's patch. Doesn't depend on YarnConfiguration in the refreshNodes
signatu
[
https://issues.apache.org/jira/browse/YARN-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461472#comment-13461472
]
Harsh J commented on YARN-97:
-
bq. It should be well documented for system not having bash instal
[
https://issues.apache.org/jira/browse/YARN-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461473#comment-13461473
]
Harsh J commented on YARN-97:
-
bq. Why don't we simply document requirements then?
We can additi
[
https://issues.apache.org/jira/browse/YARN-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462920#comment-13462920
]
Harsh J commented on YARN-130:
--
This is interesting. In trunk today, the HDFS clients do not re
[
https://issues.apache.org/jira/browse/YARN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463287#comment-13463287
]
Harsh J commented on YARN-116:
--
Ping - Can someone take a look at this? Compatible change that
[
https://issues.apache.org/jira/browse/YARN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466357#comment-13466357
]
Harsh J commented on YARN-138:
--
Thanks, Sid!
> Improve default config values f
[
https://issues.apache.org/jira/browse/YARN-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J moved MAPREDUCE-4345 to YARN-149:
-
Issue Type: New Feature (was: Improvement)
Key: YARN-149 (was: MAPREDUC
Harsh J created YARN-168:
Summary: No way to turn off virtual memory limits without turning
off physical memory limits
Key: YARN-168
URL: https://issues.apache.org/jira/browse/YARN-168
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J moved MAPREDUCE-4509 to YARN-239:
-
Component/s: (was: webapps)
nodemanager
Fix
[
https://issues.apache.org/jira/browse/YARN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reopened YARN-239:
--
Worth linking the NM if it can be done.
Apologies if no one had got back to you on the Hamlet question yet, it is a
[
https://issues.apache.org/jira/browse/YARN-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502897#comment-13502897
]
Harsh J commented on YARN-238:
--
Is there also need for this to be a "strict" need or is it good
[
https://issues.apache.org/jira/browse/YARN-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526940#comment-13526940
]
Harsh J commented on YARN-265:
--
Possible dupe of YARN-238?
> Allow locality pr
[
https://issues.apache.org/jira/browse/YARN-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J moved MAPREDUCE-4171 to YARN-281:
-
Component/s: (was: mrv2)
(was: test)
[
https://issues.apache.org/jira/browse/YARN-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J moved MAPREDUCE-3268 to YARN-284:
-
Component/s: (was: scheduler)
scheduler
Affects
[
https://issues.apache.org/jira/browse/YARN-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555176#comment-13555176
]
Harsh J commented on YARN-40:
-
Junping,
Do you mean an equivalent for the "yarn node" command fo
[
https://issues.apache.org/jira/browse/YARN-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J moved MAPREDUCE-2170 to YARN-349:
-
Tags: (was: load average, tasktracker)
Component/s: (wa
[
https://issues.apache.org/jira/browse/YARN-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-349:
-
Comment: was deleted
(was: I will return to the office on January 17th. For urgent matters,
please contact Aparna
[
https://issues.apache.org/jira/browse/YARN-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562876#comment-13562876
]
Harsh J commented on YARN-356:
--
These are already present and used (in the yarn script) but are
Harsh J created YARN-511:
Summary: ConverterUtils's getPathFromYarnURL and
getYarnUrlFromPath work with fully qualified paths alone but don't state or
check that
Key: YARN-511
URL: https://issues.apache.org/jira/browse/Y
Harsh J created YARN-552:
Summary: Expose resource metrics as part of YarnClusterMetrics
Key: YARN-552
URL: https://issues.apache.org/jira/browse/YARN-552
Project: Hadoop YARN
Issue Type: Sub-task
Harsh J created YARN-553:
Summary: Have GetNewApplicationResponse generate a directly usable
ApplicationSubmissionContext
Key: YARN-553
URL: https://issues.apache.org/jira/browse/YARN-553
Project: Hadoop YARN
Harsh J created YARN-555:
Summary: ContainerLaunchContext is buggy when it comes to setter
methods on a new instance
Key: YARN-555
URL: https://issues.apache.org/jira/browse/YARN-555
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated YARN-555:
-
Description:
If you look at the API of ContainerLaunchContext, its got setter methods, such
as for setResource, se
[
https://issues.apache.org/jira/browse/YARN-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625236#comment-13625236
]
Harsh J commented on YARN-555:
--
If I do:
{code}
Map localResources = new HashMap();
localResou
[
https://issues.apache.org/jira/browse/YARN-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved YARN-555.
--
Resolution: Duplicate
Thanks! I've resolved this as a dupe of YARN-489, which covers this.
> Con
[
https://issues.apache.org/jira/browse/YARN-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J moved MAPREDUCE-5141 to YARN-570:
-
Key: YARN-570 (was: MAPREDUCE-5141)
Project: Hadoop YARN (was: Hadoop Map/
[
https://issues.apache.org/jira/browse/YARN-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629907#comment-13629907
]
Harsh J commented on YARN-570:
--
Thanks for the report and the patch!
With this patch it now re
[
https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reopened YARN-20:
-
> More information for "yarn.resourcemanager.webapp.address" in yarn-default.xml
> -
[
https://issues.apache.org/jira/browse/YARN-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656454#comment-13656454
]
Harsh J commented on YARN-356:
--
Hey Lohit,
I think we can doc these on the yarn-env.sh templat
[
https://issues.apache.org/jira/browse/YARN-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reopened YARN-356:
--
> Add YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS to yarn.env
> -
[
https://issues.apache.org/jira/browse/YARN-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685549#comment-13685549
]
Harsh J commented on YARN-842:
--
This seems relevant
http://stackoverflow.com/questions/9433789
[
https://issues.apache.org/jira/browse/YARN-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686972#comment-13686972
]
Harsh J commented on YARN-553:
--
I'm fine with what Arun's proposed above - a single API call th
Harsh J created YARN-1200:
-
Summary: Provide a central view for rack topologies
Key: YARN-1200
URL: https://issues.apache.org/jira/browse/YARN-1200
Project: Hadoop YARN
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/YARN-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768195#comment-13768195
]
Harsh J commented on YARN-1200:
---
A reasonable regression-fixing first step is to match that o
89 matches
Mail list logo
