[jira] [Created] (YARN-2086) AmIpFilter to support REST APIs

Steve Loughran created YARN-2086: Summary: AmIpFilter to support REST APIs Key: YARN-2086 URL: https://issues.apache.org/jira/browse/YARN-2086 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-2087) YARN proxy doesn't relay verbs other than GET

Steve Loughran created YARN-2087: Summary: YARN proxy doesn't relay verbs other than GET Key: YARN-2087 URL: https://issues.apache.org/jira/browse/YARN-2087 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-2084) YARN to support REST APIs in AMs

[ https://issues.apache.org/jira/browse/YARN-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004609#comment-14004609 ] Steve Loughran commented on YARN-2084: -- Note that for Slider we worked around the

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

[ https://issues.apache.org/jira/browse/YARN-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005718#comment-14005718 ] Steve Loughran commented on YARN-2092: -- This seems like from the HADOOP-10104 patch.

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

[ https://issues.apache.org/jira/browse/YARN-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005804#comment-14005804 ] Steve Loughran commented on YARN-2092: -- I should add that the underlying issue is that

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

[ https://issues.apache.org/jira/browse/YARN-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007269#comment-14007269 ] Steve Loughran commented on YARN-2092: -- I think this should be a wontfix, as the

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

[ https://issues.apache.org/jira/browse/YARN-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010906#comment-14010906 ] Steve Loughran commented on YARN-2092: -- # code using Apache Curator was one -in YARN

[jira] [Resolved] (YARN-804) mark AbstractService init/start/stop methods as final

[ https://issues.apache.org/jira/browse/YARN-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-804. - Resolution: Won't Fix I don't think we can fix this while mocking is used to test some aspects of

[jira] [Commented] (YARN-741) Mark yarn.service package as public unstable

[ https://issues.apache.org/jira/browse/YARN-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015298#comment-14015298 ] Steve Loughran commented on YARN-741: - fixed in YARN-825 Mark yarn.service package as

[jira] [Resolved] (YARN-741) Mark yarn.service package as public unstable

[ https://issues.apache.org/jira/browse/YARN-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-741. - Resolution: Duplicate Mark yarn.service package as public unstable

[jira] [Updated] (YARN-1564) add some basic workflow YARN services

[ https://issues.apache.org/jira/browse/YARN-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1564: - Attachment: YARN-1564-001.patch Here is a package containing the set of workflow yarn services

[jira] [Updated] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-679: Priority: Major (was: Minor) Affects Version/s: 2.4.0 add an entry point that can

[jira] [Commented] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017618#comment-14017618 ] Steve Loughran commented on YARN-679: - This turns out to be useful both client-side and

[jira] [Created] (YARN-2127) Move YarnUncaughtExceptionHandler into Hadoop common

Steve Loughran created YARN-2127: Summary: Move YarnUncaughtExceptionHandler into Hadoop common Key: YARN-2127 URL: https://issues.apache.org/jira/browse/YARN-2127 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-2127) Move YarnUncaughtExceptionHandler into Hadoop common

[ https://issues.apache.org/jira/browse/YARN-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019165#comment-14019165 ] Steve Loughran commented on YARN-2127: -- I can incorporate this into YARN-679 easily

[jira] [Updated] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-679: Attachment: YARN-679-002.patch This (big) patch provides the service launcher with # a

[jira] [Updated] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-679: Attachment: org.apache.hadoop.servic...mon 3.0.0-SNAPSHOT API).pdf This is the package javadoc add

[jira] [Updated] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-679: Attachment: YARN-679-002.patch add an entry point that can start any Yarn service

[jira] [Commented] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020769#comment-14020769 ] Steve Loughran commented on YARN-679: - some of the compiler warning are about use of

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027357#comment-14027357 ] Steve Loughran commented on YARN-2139: -- I don't think I was clear enough, sorry HDFS

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027820#comment-14027820 ] Steve Loughran commented on YARN-2139: -- well, I am happy to be wrong here. I was of

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14037828#comment-14037828 ] Steve Loughran commented on YARN-941: - [~vanzin], the issue here is that the AMRM token

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038041#comment-14038041 ] Steve Loughran commented on YARN-1039: -- marking as depended on by YARN-896. I would

[jira] [Commented] (YARN-2190) Provide a Windows container executor that can limit memory and CPU

[ https://issues.apache.org/jira/browse/YARN-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039973#comment-14039973 ] Steve Loughran commented on YARN-2190: -- # what would the implications for the move

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039976#comment-14039976 ] Steve Loughran commented on YARN-1039: -- # I'd make the long-lived flag a container

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041105#comment-14041105 ] Steve Loughran commented on YARN-1039: -- I see. I'd assume that the service flag would

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042370#comment-14042370 ] Steve Loughran commented on YARN-1039: -- bq. We need to have another flag to indicate

[jira] [Commented] (YARN-614) Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042910#comment-14042910 ] Steve Loughran commented on YARN-614: - I like this, but need to note one thing: our AM

[jira] [Commented] (YARN-1727) provide (async) application lifecycle events to management tools

[ https://issues.apache.org/jira/browse/YARN-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044003#comment-14044003 ] Steve Loughran commented on YARN-1727: -- Yes, this can and should be appilcation

[jira] [Updated] (YARN-2223) NPE on ResourceManager recover

[ https://issues.apache.org/jira/browse/YARN-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2223: - Environment: JDK 8u5 NPE on ResourceManager recover --

[jira] [Updated] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-679: Attachment: YARN-679-003.patch Revised patch # uses reflection to load the HDFS and YARN

[jira] [Commented] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

[ https://issues.apache.org/jira/browse/YARN-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047111#comment-14047111 ] Steve Loughran commented on YARN-2065: -- I'll try to run my code against this patch

[jira] [Updated] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

[ https://issues.apache.org/jira/browse/YARN-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2065: - Attachment: YARN-2065-002.patch This is the previous patch, in sync with trunk AM cannot create

[jira] [Commented] (YARN-1565) Add a way for YARN clients to get critical YARN system properties from the RM

[ https://issues.apache.org/jira/browse/YARN-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048704#comment-14048704 ] Steve Loughran commented on YARN-1565: -- I think this should be part of the REST API

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049758#comment-14049758 ] Steve Loughran commented on YARN-2139: -- looks a good first draft # unless this does

[jira] [Updated] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

[ https://issues.apache.org/jira/browse/YARN-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2065: - Attachment: YARN-2065-003.patch correction: this is the version that compiles against trunk.

[jira] [Commented] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

[ https://issues.apache.org/jira/browse/YARN-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050521#comment-14050521 ] Steve Loughran commented on YARN-2065: -- With Jenkins happy, I'm +1 on this patch; it

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14053744#comment-14053744 ] Steve Loughran commented on YARN-2242: -- +1 for retaining/propagating as much

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054667#comment-14054667 ] Steve Loughran commented on YARN-2242: -- thinking about this, one thing I'd like for my

[jira] [Commented] (YARN-1111) NM containerlogs servlet can't handle logs of more than a GB

[ https://issues.apache.org/jira/browse/YARN-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13782078#comment-13782078 ] Steve Loughran commented on YARN-: -- investigate how the logs get copied back from

[jira] [Commented] (YARN-1111) NM containerlogs servlet can't handle logs of more than a GB

[ https://issues.apache.org/jira/browse/YARN-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13782080#comment-13782080 ] Steve Loughran commented on YARN-: -- ignore that last comment, note to myself NM

[jira] [Commented] (YARN-913) Add a way to register long-lived services in a YARN cluster

[ https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786229#comment-13786229 ] Steve Loughran commented on YARN-913: - what I'm doing right now is just enumerating all

[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=13786318#comment-13786318 ] Steve Loughran commented on YARN-445: - c-break is special in that it can talk to the

[jira] [Commented] (YARN-1139) [Umbrella] Convert all RM components to Services

[ https://issues.apache.org/jira/browse/YARN-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797804#comment-13797804 ] Steve Loughran commented on YARN-1139: -- # you don't need to convert any exceptions

[jira] [Commented] (YARN-913) Add a way to register long-lived services in a YARN cluster

[ https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799170#comment-13799170 ] Steve Loughran commented on YARN-913: - # your design reminds me a lot of bonjour, just a

[jira] [Commented] (YARN-614) Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799180#comment-13799180 ] Steve Loughran commented on YARN-614: - Chris -are you using this? For long lived

[jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests

[ https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799189#comment-13799189 ] Steve Loughran commented on YARN-796: - I'd like to be able to allocate different labels

[jira] [Commented] (YARN-896) Roll up for long-lived services in YARN

[ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799199#comment-13799199 ] Steve Loughran commented on YARN-896: - Link to YARN-810, CGroup limits for CPU Roll up

[jira] [Commented] (YARN-1305) RMHAProtocolService#serviceInit should handle HAUtil's IllegalArgumentException

[ https://issues.apache.org/jira/browse/YARN-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13799883#comment-13799883 ] Steve Loughran commented on YARN-1305: -- Looks OK, except that would recommend using

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805512#comment-13805512 ] Steve Loughran commented on YARN-941: - Ignoring HDFS, updated Yarn RM tokens (and the

[jira] [Created] (YARN-1360) Rework Distributed Shell to be a better model of how people should write YARN applications

Steve Loughran created YARN-1360: Summary: Rework Distributed Shell to be a better model of how people should write YARN applications Key: YARN-1360 URL: https://issues.apache.org/jira/browse/YARN-1360

[jira] [Commented] (YARN-1360) Rework Distributed Shell to be a better model of how people should write YARN applications

[ https://issues.apache.org/jira/browse/YARN-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808058#comment-13808058 ] Steve Loughran commented on YARN-1360: -- I'm not volunteering to do this, though I now

[jira] [Commented] (YARN-1374) Resource Manager fails to start due to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809085#comment-13809085 ] Steve Loughran commented on YARN-1374: -- If this exists, my code. I'd put the list into

[jira] [Commented] (YARN-1374) Resource Manager fails to start due to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810364#comment-13810364 ] Steve Loughran commented on YARN-1374: -- while this patch fixes a symptom, it doesn't

[jira] [Commented] (YARN-1374) Resource Manager fails to start due to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813346#comment-13813346 ] Steve Loughran commented on YARN-1374: -- [~bikassaha] -if we clone the list before

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13815946#comment-13815946 ] Steve Loughran commented on YARN-941: - Thinking some more, if the AM just terminated

[jira] [Commented] (YARN-914) Support graceful decommission of nodemanager

[ https://issues.apache.org/jira/browse/YARN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817145#comment-13817145 ] Steve Loughran commented on YARN-914: - YARN-1394 adds the need for AMs to be told of NM

[jira] [Created] (YARN-1394) RM to inform AMs when a container completed due to NM going offline -planned or unplanned

Steve Loughran created YARN-1394: Summary: RM to inform AMs when a container completed due to NM going offline -planned or unplanned Key: YARN-1394 URL: https://issues.apache.org/jira/browse/YARN-1394

[jira] [Commented] (YARN-896) Roll up for long-lived services in YARN

[ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817148#comment-13817148 ] Steve Loughran commented on YARN-896: - Link to YARN-1394: RM to inform NMs when a

[jira] [Commented] (YARN-1404) Add support for unmanaged containers

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821181#comment-13821181 ] Steve Loughran commented on YARN-1404: -- # I'd be inclined to treat this as a special

[jira] [Commented] (YARN-149) ResourceManager (RM) High-Availability (HA)

[ https://issues.apache.org/jira/browse/YARN-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13828948#comment-13828948 ] Steve Loughran commented on YARN-149: - I want to warn that HADOOP-9905 is going to drop

[jira] [Created] (YARN-1437) Add way for YARN client to determine the resource limits of a queue before creating the AM

Steve Loughran created YARN-1437: Summary: Add way for YARN client to determine the resource limits of a queue before creating the AM Key: YARN-1437 URL: https://issues.apache.org/jira/browse/YARN-1437

[jira] [Created] (YARN-1438) When a container fails, the text of the exception isn't included in the diagnostics

Steve Loughran created YARN-1438: Summary: When a container fails, the text of the exception isn't included in the diagnostics Key: YARN-1438 URL: https://issues.apache.org/jira/browse/YARN-1438

[jira] [Commented] (YARN-1438) When a container fails, the text of the exception isn't included in the diagnostics

[ https://issues.apache.org/jira/browse/YARN-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13829995#comment-13829995 ] Steve Loughran commented on YARN-1438: -- Here's an example, we know the container

[jira] [Commented] (YARN-1438) When a container fails, the text of the exception isn't included in the diagnostics

[ https://issues.apache.org/jira/browse/YARN-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13829997#comment-13829997 ] Steve Loughran commented on YARN-1438: -- the issue here is that while the NM logs

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=1382#comment-1382 ] Steve Loughran commented on YARN-778: - YARN-257 may be the cause, but this is about

[jira] [Moved] (YARN-1442) change yarn minicluster base directory via system property

[ https://issues.apache.org/jira/browse/YARN-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran moved HADOOP-10122 to YARN-1442: --- Affects Version/s: (was: 2.2.0) 2.2.0

[jira] [Created] (YARN-1456) IntelliJ IDEA gets dependencies wrong for hadoop-yarn-server-resourcemanager

Steve Loughran created YARN-1456: Summary: IntelliJ IDEA gets dependencies wrong for hadoop-yarn-server-resourcemanager Key: YARN-1456 URL: https://issues.apache.org/jira/browse/YARN-1456 Project:

[jira] [Updated] (YARN-1456) IntelliJ IDEA gets dependencies wrong for hadoop-yarn-server-resourcemanager

[ https://issues.apache.org/jira/browse/YARN-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1456: - Attachment: YARN-1456-001.patch The fix for this is trivial: explicitly add a hadoop-commons

[jira] [Commented] (YARN-1390) Provide a way to capture source of an application to be queried through REST or Java Client APIs

[ https://issues.apache.org/jira/browse/YARN-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13836410#comment-13836410 ] Steve Loughran commented on YARN-1390: -- # Some limits on tag size is going to be

[jira] [Commented] (YARN-1390) Provide a way to capture source of an application to be queried through REST or Java Client APIs

[ https://issues.apache.org/jira/browse/YARN-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13836823#comment-13836823 ] Steve Loughran commented on YARN-1390: -- oh and restrict the tag names to stuff that

[jira] [Updated] (YARN-1438) When a container fails, the text of the exception isn't included in the diagnostics

[ https://issues.apache.org/jira/browse/YARN-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1438: - Attachment: YARN-1438-001.patch Include the exception message in the diagnostics. No test on the

[jira] [Commented] (YARN-1470) Add audience annotation to MiniYARNCluster

[ https://issues.apache.org/jira/browse/YARN-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13838748#comment-13838748 ] Steve Loughran commented on YARN-1470: -- It's essential for YARN app test, so: public +

[jira] [Commented] (YARN-1438) When a container fails, the text of the exception isn't included in the diagnostics

[ https://issues.apache.org/jira/browse/YARN-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13841299#comment-13841299 ] Steve Loughran commented on YARN-1438: -- [~ozawa] I'll put up a trace the next time i

[jira] [Commented] (YARN-1492) truly shared cache for jars (jobjar/libjar)

[ https://issues.apache.org/jira/browse/YARN-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845246#comment-13845246 ] Steve Loughran commented on YARN-1492: -- bq. obviously: add a specific exception to

[jira] [Created] (YARN-1554) add an env variable for the YARN AM classpath

Steve Loughran created YARN-1554: Summary: add an env variable for the YARN AM classpath Key: YARN-1554 URL: https://issues.apache.org/jira/browse/YARN-1554 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1554) add an env variable for the YARN AM classpath

[ https://issues.apache.org/jira/browse/YARN-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13860131#comment-13860131 ] Steve Loughran commented on YARN-1554: -- As noted in

[jira] [Created] (YARN-1556) NPE getting application report with a null appId

Steve Loughran created YARN-1556: Summary: NPE getting application report with a null appId Key: YARN-1556 URL: https://issues.apache.org/jira/browse/YARN-1556 Project: Hadoop YARN Issue

[jira] [Created] (YARN-1564) add some basic workflow YARN services

Steve Loughran created YARN-1564: Summary: add some basic workflow YARN services Key: YARN-1564 URL: https://issues.apache.org/jira/browse/YARN-1564 Project: Hadoop YARN Issue Type: New

[jira] [Commented] (YARN-1564) add some basic workflow YARN services

[ https://issues.apache.org/jira/browse/YARN-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862988#comment-13862988 ] Steve Loughran commented on YARN-1564: -- Services are all in

[jira] [Created] (YARN-1565) Add a way for YARN clients to get critical YARN system properties from the RM

Steve Loughran created YARN-1565: Summary: Add a way for YARN clients to get critical YARN system properties from the RM Key: YARN-1565 URL: https://issues.apache.org/jira/browse/YARN-1565 Project:

[jira] [Commented] (YARN-896) Roll up for long-lived services in YARN

[ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864209#comment-13864209 ] Steve Loughran commented on YARN-896: - Link to YARN-1489: umbrella JAR for work

[jira] [Commented] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart

[ https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864212#comment-13864212 ] Steve Loughran commented on YARN-1489: -- regarding the rebinding problem, YARN-913

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864237#comment-13864237 ] Steve Loughran commented on YARN-1490: -- How will the AM get notified of its existing

[jira] [Commented] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart

[ https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864365#comment-13864365 ] Steve Loughran commented on YARN-1489: -- Actually, the simplest way for an AM to work

[jira] [Commented] (YARN-1041) Protocol changes for RM to bind and notify a restarted AM of existing containers

[ https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865223#comment-13865223 ] Steve Loughran commented on YARN-1041: -- Looks good as an API for an AM to work with #

[jira] [Commented] (YARN-1566) Change distributed-shell to retain containers from previous AppAttempt

[ https://issues.apache.org/jira/browse/YARN-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867728#comment-13867728 ] Steve Loughran commented on YARN-1566: -- Looks good to me -my AM will actually grab the

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868739#comment-13868739 ] Steve Loughran commented on YARN-888: - +1 to the don't add dependencies here comment

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13869714#comment-13869714 ] Steve Loughran commented on YARN-888: - --I've no objections, so +1 from me clean up

[jira] [Commented] (YARN-1104) NMs to support rolling logs of stdout stderr

[ https://issues.apache.org/jira/browse/YARN-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871834#comment-13871834 ] Steve Loughran commented on YARN-1104: -- in Hoya we're setting up log4j for rolling

[jira] [Commented] (YARN-1601) 3rd party JARs are missing from hadoop-dist output

[ https://issues.apache.org/jira/browse/YARN-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871837#comment-13871837 ] Steve Loughran commented on YARN-1601: -- Makes sense. Let me do a branch-2 build before

[jira] [Commented] (YARN-1603) Remove two *.orig files which were unexpectedly committed

[ https://issues.apache.org/jira/browse/YARN-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871845#comment-13871845 ] Steve Loughran commented on YARN-1603: -- +1 Remove two *.orig files which were

[jira] [Resolved] (YARN-1604) Remove unnecessary files TestFifoScheduler.java.orig and FairScheduler.java.orig

[ https://issues.apache.org/jira/browse/YARN-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-1604. -- Resolution: Duplicate Remove unnecessary files TestFifoScheduler.java.orig and

[jira] [Commented] (YARN-1601) 3rd party JARs are missing from hadoop-dist output

[ https://issues.apache.org/jira/browse/YARN-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871920#comment-13871920 ] Steve Loughran commented on YARN-1601: -- before the patch {code} $ find

[jira] [Commented] (YARN-1601) 3rd party JARs are missing from hadoop-dist output

[ https://issues.apache.org/jira/browse/YARN-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871921#comment-13871921 ] Steve Loughran commented on YARN-1601: -- after the patch {code}

[jira] [Commented] (YARN-1601) 3rd party JARs are missing from hadoop-dist output

[ https://issues.apache.org/jira/browse/YARN-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13871923#comment-13871923 ] Steve Loughran commented on YARN-1601: -- confirmed that problem exists patch does as

[jira] [Commented] (YARN-1663) NPE in FifoScheduler.assignContainers

[ https://issues.apache.org/jira/browse/YARN-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884329#comment-13884329 ] Steve Loughran commented on YARN-1663: -- {code} 2014-01-28 16:56:00,665 [JUnit] INFO

[jira] [Moved] (YARN-1663) NPE in FifoScheduler.assignContainers

[ https://issues.apache.org/jira/browse/YARN-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran moved MAPREDUCE-5737 to YARN-1663: - Component/s: (was: scheduler)

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884366#comment-13884366 ] Steve Loughran commented on YARN-1490: -- I'm just going to add some AM implementation

[jira] [Commented] (YARN-1663) NPE in FifoScheduler.assignContainers

[ https://issues.apache.org/jira/browse/YARN-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884380#comment-13884380 ] Steve Loughran commented on YARN-1663: -- There's a lot of similarity to YARN-1572,

<    1   2   3   4   5   6   7   8   9   10   >