[
https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600167#comment-13600167
]
Chris Riccomini commented on YARN-417:
--------------------------------------
Perhaps this helps:
https://builds.apache.org/job/PreCommit-YARN-Build/496/artifact/trunk/patchprocess/patchEclipseOutput.txt
I wonder if this was fixed elsewhere? I took a look at hadoop-common's pom.xml,
as well as its parents. The only thing that has changed recently (the 6th) was
the hadoop-common pom.xml. Seems strange.
Line 256 in:
http://svn.apache.org/viewvc/hadoop/common/trunk/hadoop-common-project/hadoop-common/pom.xml?view=markup
Is somewhat revealing. A bit of googling revealed:
https://issues.apache.org/jira/browse/HADOOP-9251
Seems it's related to Hudson not cleaning up/setting up properly.
> Add a poller that allows the AM to receive notifications when it is assigned
> containers
> ---------------------------------------------------------------------------------------
>
> Key: YARN-417
> URL: https://issues.apache.org/jira/browse/YARN-417
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, applications
> Affects Versions: 2.0.3-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: AMRMClientAsync-1.java, AMRMClientAsync.java,
> YARN-417-1.patch, YARN-417-2.patch, YARN-417-3.patch, YARN-417-4.patch,
> YARN-417-4.patch, YARN-417.patch, YarnAppMaster.java,
> YarnAppMasterListener.java
>
>
> Writing AMs would be easier for some if they did not have to handle
> heartbeating to the RM on their own.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
