[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-530-011.patch Updated patch which makes start/init no-ops if called from that

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117-011.patch patch in sync w/ YARN-530-011; as well as init/start being no-ops on

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117-013.patch in sync w/ YARN-530-013. # move the service listener registration

[jira] [Updated] (YARN-746) rename Service.register() and Service.unregister() to registerServiceListener() unregisterServiceListener() respectively

[ https://issues.apache.org/jira/browse/YARN-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-746: Attachment: YARN-746-001.patch Patch -designed to go in after the big YARN-117 commit -it updates

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-530-014.patch Pulled the {{ServiceShutdownHook}} code off to YARN-679, this

[jira] [Updated] (YARN-678) Delete FilterService

[ https://issues.apache.org/jira/browse/YARN-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-678: Attachment: YARN-678-001.patch deletes filter service. This patch is built on the YARN-746

[jira] [Assigned] (YARN-746) rename Service.register() and Service.unregister() to registerServiceListener() unregisterServiceListener() respectively

[ https://issues.apache.org/jira/browse/YARN-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran reassigned YARN-746: --- Assignee: Steve Loughran rename Service.register() and Service.unregister() to

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117-016.patch This appears to be Mockito changing things, marking them as final

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: MAPREDUCE-5298-016.patch Patch in sync w/ YARN-530-016.patch Enhance

[jira] [Commented] (YARN-635) Rename YarnRemoteException to YarnException

[ https://issues.apache.org/jira/browse/YARN-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13674202#comment-13674202 ] Steve Loughran commented on YARN-635: - I've just noticed this and am dealing with the

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-530-018.patch vinod -thanks for trying to defeat findbugs. Here is your patch

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117-018.patch patch applying vinod's changes to YARN-530 and migration to the

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-117-019.patch # make sure addService, removeService and service iteration are all

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: (was: MAPREDUCE-5298-016.patch) Enhance YARN service model

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-530-019.patch # make sure addService, removeService and service iteration are all

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117-019.patch # make sure addService, removeService and service iteration are all

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-530-020.patch There's no change from -19 except an extra line of logging in

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117-020.patch as with YARN-530-020 There's no change from -19 except an extra line

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-530-021.patch This patch manages all the MR services properly -the change was

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117-021.patch Patch incorporating the sync changes of the '530-021 patch.

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

Steve Loughran created YARN-770: --- Summary: NPE NodeStatusUpdaterImpl Key: YARN-770 URL: https://issues.apache.org/jira/browse/YARN-770 Project: Hadoop YARN Issue Type: Bug

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

[ https://issues.apache.org/jira/browse/YARN-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677316#comment-13677316 ] Steve Loughran commented on YARN-770: - A miniYARN cluster that was working just failed

[jira] [Commented] (YARN-773) Move YarnRuntimeException from package api.yarn to api.yarn.exceptions

[ https://issues.apache.org/jira/browse/YARN-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677906#comment-13677906 ] Steve Loughran commented on YARN-773: - # Given the grief I had with the last exception

[jira] [Commented] (YARN-773) Move YarnRuntimeException from package api.yarn to api.yarn.exceptions

[ https://issues.apache.org/jira/browse/YARN-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677908#comment-13677908 ] Steve Loughran commented on YARN-773: - I like new exception classes for testability. If

[jira] [Commented] (YARN-773) Move YarnRuntimeException from package api.yarn to api.yarn.exceptions

[ https://issues.apache.org/jira/browse/YARN-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677917#comment-13677917 ] Steve Loughran commented on YARN-773: - (ignore last comment, wrong JIRA)

[jira] [Created] (YARN-793) ApplicationReport to have a useful toString() method

Steve Loughran created YARN-793: --- Summary: ApplicationReport to have a useful toString() method Key: YARN-793 URL: https://issues.apache.org/jira/browse/YARN-793 Project: Hadoop YARN Issue

[jira] [Created] (YARN-794) YarnClientImpl.submitApplication() to add a timeout

Steve Loughran created YARN-794: --- Summary: YarnClientImpl.submitApplication() to add a timeout Key: YARN-794 URL: https://issues.apache.org/jira/browse/YARN-794 Project: Hadoop YARN Issue

[jira] [Resolved] (YARN-794) YarnClientImpl.submitApplication() to add a timeout

[ https://issues.apache.org/jira/browse/YARN-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-794. - Resolution: Duplicate Fix Version/s: 3.0.0 2.1.0-beta

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117-022.patch rebased to this trunk of June 10; all tests passing

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-530-022.patch Patch in sync w/ YARN-117-022: rebased to trunk of June 10; all tests

[jira] [Resolved] (YARN-125) Make Yarn Client service shutdown operations robust

[ https://issues.apache.org/jira/browse/YARN-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-125. - Resolution: Fixed Fix Version/s: 2.1.0-beta Make Yarn Client service shutdown

[jira] [Resolved] (YARN-123) Make yarn Resource Manager services robust against shutdown

[ https://issues.apache.org/jira/browse/YARN-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-123. - Resolution: Fixed Fix Version/s: 2.1.0-beta Make yarn Resource Manager services robust

[jira] [Resolved] (YARN-124) Make Yarn Node Manager services robust against shutdown

[ https://issues.apache.org/jira/browse/YARN-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-124. - Resolution: Fixed Fix Version/s: 2.1.0-beta Make Yarn Node Manager services robust

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

Steve Loughran created YARN-804: --- Summary: mark AbstractService init/start/stop methods as final Key: YARN-804 URL: https://issues.apache.org/jira/browse/YARN-804 Project: Hadoop YARN Issue

[jira] [Updated] (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 updated YARN-804: Attachment: YARN-804-001.patch Marking the methods as final, and fixing a (recent) test that needs

[jira] [Commented] (YARN-811) Add a set of final _init/_start/_stop methods to CompositeService

[ https://issues.apache.org/jira/browse/YARN-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682832#comment-13682832 ] Steve Loughran commented on YARN-811: - {{CompositeService extends AbstractServoce}},

[jira] [Resolved] (YARN-811) Add a set of final _init/_start/_stop methods to CompositeService

[ https://issues.apache.org/jira/browse/YARN-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-811. - Resolution: Duplicate marking as contained by YARN-804 - {{CompositeService}} is a subclass of

[jira] [Commented] (YARN-811) Add a set of final _init/_start/_stop methods to CompositeService

[ https://issues.apache.org/jira/browse/YARN-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684165#comment-13684165 ] Steve Loughran commented on YARN-811: - Siddarth -I see. I went through all the

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13684173#comment-13684173 ] Steve Loughran commented on YARN-804: - # code calls init() or start() on a composite

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

[ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13699314#comment-13699314 ] Steve Loughran commented on YARN-896: - Based on our Hoya, HBase on YARN work: * we need

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

Steve Loughran created YARN-913: --- Summary: Add a way to register long-lived services in a YARN cluster Key: YARN-913 URL: https://issues.apache.org/jira/browse/YARN-913 Project: Hadoop YARN

[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=13704925#comment-13704925 ] Steve Loughran commented on YARN-913: - You can list running apps today, but # anyone can

[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=13707733#comment-13707733 ] Steve Loughran commented on YARN-913: - HDFS-4849 has shown value in having some

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

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

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

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

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725372#comment-13725372 ] Steve Loughran commented on YARN-972: - I'd argue against fractional core assignment not

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13726380#comment-13726380 ] Steve Loughran commented on YARN-972: - bq. Nodes in probably the majority of clusters

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

[ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727476#comment-13727476 ] Steve Loughran commented on YARN-896: - YARN-1011 - speculative containers- may be useful

[jira] [Commented] (YARN-1011) [Umbrella] RM should dynamically schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727582#comment-13727582 ] Steve Loughran commented on YARN-1011: -- Feature creep: could we have a way to

[jira] [Created] (YARN-1018) prereqeq check for AMRMClient.ContainerRequest relaxLocality flag wrong

Steve Loughran created YARN-1018: Summary: prereqeq check for AMRMClient.ContainerRequest relaxLocality flag wrong Key: YARN-1018 URL: https://issues.apache.org/jira/browse/YARN-1018 Project: Hadoop

[jira] [Updated] (YARN-1018) prereq check for AMRMClient.ContainerRequest relaxLocality flag wrong

[ https://issues.apache.org/jira/browse/YARN-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1018: - Summary: prereq check for AMRMClient.ContainerRequest relaxLocality flag wrong (was: prereqeq

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729833#comment-13729833 ] Steve Loughran commented on YARN-1024: -- I was the one trying to convince Sandy that a

[jira] [Commented] (YARN-1018) prereq check for AMRMClient.ContainerRequest relaxLocality flag wrong

[ https://issues.apache.org/jira/browse/YARN-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729890#comment-13729890 ] Steve Loughran commented on YARN-1018: -- OK, but there's a risk that an empty array has

[jira] [Commented] (YARN-1035) NPE when trying to create an error message response of RPC

[ https://issues.apache.org/jira/browse/YARN-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731063#comment-13731063 ] Steve Loughran commented on YARN-1035: -- {code} 8]] INFO DataNode.clienttrace

[jira] [Created] (YARN-1035) NPE when trying to create an error message response of RPC

Steve Loughran created YARN-1035: Summary: NPE when trying to create an error message response of RPC Key: YARN-1035 URL: https://issues.apache.org/jira/browse/YARN-1035 Project: Hadoop YARN

[jira] [Commented] (YARN-1035) NPE when trying to create an error message response of RPC

[ https://issues.apache.org/jira/browse/YARN-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731064#comment-13731064 ] Steve Loughran commented on YARN-1035: -- Looking up the stack, it's in {code}

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

Steve Loughran created YARN-1039: Summary: Add resource for YARN container requests to indicate long lived Key: YARN-1039 URL: https://issues.apache.org/jira/browse/YARN-1039 Project: Hadoop YARN

[jira] [Created] (YARN-1040) Add ability to execute multiple programs in the same long-lived container

Steve Loughran created YARN-1040: Summary: Add ability to execute multiple programs in the same long-lived container Key: YARN-1040 URL: https://issues.apache.org/jira/browse/YARN-1040 Project:

[jira] [Commented] (YARN-1041) 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=13732207#comment-13732207 ] Steve Loughran commented on YARN-1041: -- This is not something that MR could

[jira] [Commented] (YARN-1016) Define a HDFS based repository that allows YARN services to share resources

[ https://issues.apache.org/jira/browse/YARN-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13732231#comment-13732231 ] Steve Loughran commented on YARN-1016: -- We can re-use existing artifacts in HDFS today

[jira] [Created] (YARN-1042) add ability to specify affinity/anti-affinity in container requests

Steve Loughran created YARN-1042: Summary: add ability to specify affinity/anti-affinity in container requests Key: YARN-1042 URL: https://issues.apache.org/jira/browse/YARN-1042 Project: Hadoop YARN

[jira] [Commented] (YARN-1041) 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=13732935#comment-13732935 ] Steve Loughran commented on YARN-1041: -- AFAIK, currently, if the AM fails then all its

[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=13734135#comment-13734135 ] Steve Loughran commented on YARN-679: - I've been evolving this driven by the Hoya

[jira] [Commented] (YARN-1042) add ability to specify affinity/anti-affinity in container requests

[ https://issues.apache.org/jira/browse/YARN-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735386#comment-13735386 ] Steve Loughran commented on YARN-1042: -- Maybe -but now that Hadoop topologies can

[jira] [Created] (YARN-1054) Invalid state transition exception caught when tearing down a (mini) cluster

Steve Loughran created YARN-1054: Summary: Invalid state transition exception caught when tearing down a (mini) cluster Key: YARN-1054 URL: https://issues.apache.org/jira/browse/YARN-1054 Project:

[jira] [Commented] (YARN-1054) Invalid state transition exception caught when tearing down a (mini) cluster

[ https://issues.apache.org/jira/browse/YARN-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735545#comment-13735545 ] Steve Loughran commented on YARN-1054: -- logs with stack {code} 2013-08-09 16:46:31,208

[jira] [Commented] (YARN-624) Support gang scheduling in the AM RM protocol

[ https://issues.apache.org/jira/browse/YARN-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735965#comment-13735965 ] Steve Loughran commented on YARN-624: - I now think we can't just offload off this to the

[jira] [Commented] (YARN-1059) IllegalArgumentException while starting YARN

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737073#comment-13737073 ] Steve Loughran commented on YARN-1059: -- It looks the root cause is that you've got

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

[ https://issues.apache.org/jira/browse/YARN-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742528#comment-13742528 ] Steve Loughran commented on YARN-1070: -- I see this during MiniYARN cluster teardown,

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

[ https://issues.apache.org/jira/browse/YARN-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742535#comment-13742535 ] Steve Loughran commented on YARN-1070: -- BTW, notice that

[jira] [Updated] (YARN-1073) NM to recognise when it can't span process and stop accepting containers

[ https://issues.apache.org/jira/browse/YARN-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1073: - Priority: Minor (was: Major) NM to recognise when it can't span process and stop accepting

[jira] [Created] (YARN-1073) NM to recognise when it can't span process and stop accepting containers

Steve Loughran created YARN-1073: Summary: NM to recognise when it can't span process and stop accepting containers Key: YARN-1073 URL: https://issues.apache.org/jira/browse/YARN-1073 Project: Hadoop

[jira] [Commented] (YARN-1073) NM to recognise when it can't span process and stop accepting containers

[ https://issues.apache.org/jira/browse/YARN-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742568#comment-13742568 ] Steve Loughran commented on YARN-1073: -- My AM asked for more containers than my laptop

[jira] [Updated] (YARN-1073) NM to recognise when it can't spawn process and stop accepting containers

[ https://issues.apache.org/jira/browse/YARN-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1073: - Summary: NM to recognise when it can't spawn process and stop accepting containers (was: NM to

[jira] [Commented] (YARN-1073) NM to recognise when it can't spawn process and stop accepting containers

[ https://issues.apache.org/jira/browse/YARN-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742571#comment-13742571 ] Steve Loughran commented on YARN-1073: -- Note that this happened when setting up the

[jira] [Commented] (YARN-1075) AsyncDispatcher and ResourceTrackerService violate serviceStart() semantics

[ https://issues.apache.org/jira/browse/YARN-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742633#comment-13742633 ] Steve Loughran commented on YARN-1075: -- Karthik, Both the named services extend

[jira] [Updated] (YARN-1075) AsyncDispatcher and ResourceTrackerService violate serviceStart() semantics

[ https://issues.apache.org/jira/browse/YARN-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1075: - Priority: Minor (was: Major) downgrading to minor as state management logic is not in

[jira] [Assigned] (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 reassigned YARN-679: --- Assignee: Steve Loughran add an entry point that can start any Yarn service

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

[ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744029#comment-13744029 ] Steve Loughran commented on YARN-896: - Chris -I use the bar today as measure of expected

[jira] [Created] (YARN-1092) RM proxy URLs invalid when running without a YARN proxy service

Steve Loughran created YARN-1092: Summary: RM proxy URLs invalid when running without a YARN proxy service Key: YARN-1092 URL: https://issues.apache.org/jira/browse/YARN-1092 Project: Hadoop YARN

[jira] [Commented] (YARN-1092) RM proxy URLs invalid when running without a YARN proxy service

[ https://issues.apache.org/jira/browse/YARN-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13747896#comment-13747896 ] Steve Loughran commented on YARN-1092: -- # My AM generates a URL to the hbase master,

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

Steve Loughran created YARN-1104: Summary: NMs to support rolling logs of stdout stderr Key: YARN-1104 URL: https://issues.apache.org/jira/browse/YARN-1104 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-1105) RM or YarnClient to notify AMs if resource requests cannot be satisfied

Steve Loughran created YARN-1105: Summary: RM or YarnClient to notify AMs if resource requests cannot be satisfied Key: YARN-1105 URL: https://issues.apache.org/jira/browse/YARN-1105 Project: Hadoop

[jira] [Commented] (YARN-1105) RM or YarnClient to notify AMs if resource requests cannot be satisfied

[ https://issues.apache.org/jira/browse/YARN-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751669#comment-13751669 ] Steve Loughran commented on YARN-1105: -- This could be done in the AM by tracking when

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

Steve Loughran created YARN-: Summary: NM containerlogs servlet can't handle logs of more than a GB Key: YARN- URL: https://issues.apache.org/jira/browse/YARN- Project: Hadoop YARN

[jira] [Commented] (YARN-173) Page navigation support for container logs page

[ https://issues.apache.org/jira/browse/YARN-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13752616#comment-13752616 ] Steve Loughran commented on YARN-173: - I'm marking as relates YARN- rather than

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

[ https://issues.apache.org/jira/browse/YARN-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13752612#comment-13752612 ] Steve Loughran commented on YARN-1001: -- I'd recommend using {{toLowerCase(EN_US)}} in

[jira] [Reopened] (YARN-981) YARN/MR2/Job-history /logs link does not have correct content

[ https://issues.apache.org/jira/browse/YARN-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran reopened YARN-981: - branch-2.1 doesn't compile after this patch is merged in {code} [ERROR]

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

[ https://issues.apache.org/jira/browse/YARN-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13757597#comment-13757597 ] Steve Loughran commented on YARN-1001: -- As long as everyone is happy with the URL

[jira] [Created] (YARN-1143) Restrict the names that apps and types can have

Steve Loughran created YARN-1143: Summary: Restrict the names that apps and types can have Key: YARN-1143 URL: https://issues.apache.org/jira/browse/YARN-1143 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-1143) Restrict the names that apps and types can have

[ https://issues.apache.org/jira/browse/YARN-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13758978#comment-13758978 ] Steve Loughran commented on YARN-1143: -- thinking about this some more, I'd like the

[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=13758985#comment-13758985 ] Steve Loughran commented on YARN-913: - I think YARN-1143 might be relevant here:

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

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran reopened YARN-957: - this breaks the branch-2 build {code} [INFO]

[jira] [Commented] (YARN-1155) RM should resolve hostnames/ips in include/exclude files to support matching against both hostnames and ips

[ https://issues.apache.org/jira/browse/YARN-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760128#comment-13760128 ] Steve Loughran commented on YARN-1155: -- This would need to work for clusters where DNS

[jira] [Moved] (YARN-1160) allow admins to force app deployment on a specific host

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

[jira] [Commented] (YARN-1151) Ability to configure auxiliary services from HDFS-based JAR files

[ https://issues.apache.org/jira/browse/YARN-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760146#comment-13760146 ] Steve Loughran commented on YARN-1151: -- it gets more complex once you add in failure

[jira] [Commented] (YARN-1160) allow admins to force app deployment on a specific host

[ https://issues.apache.org/jira/browse/YARN-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760210#comment-13760210 ] Steve Loughran commented on YARN-1160: -- -Yes, and if you don't get that container it

[jira] [Created] (YARN-1164) maven Junit dependency should be test only

Steve Loughran created YARN-1164: Summary: maven Junit dependency should be test only Key: YARN-1164 URL: https://issues.apache.org/jira/browse/YARN-1164 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-1164) maven Junit dependency should be test only

[ https://issues.apache.org/jira/browse/YARN-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1164: - Attachment: HADOOP-9935-001.patch Patch from André Kelpe for HADOOP-9935; this JIRA is to test

[jira] [Commented] (YARN-1160) allow admins to force app deployment on a specific host

[ https://issues.apache.org/jira/browse/YARN-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761094#comment-13761094 ] Steve Loughran commented on YARN-1160: -- yes. use case is deploying services cluster

  1   2   3   4   5   6   7   8   9   10   >