[
https://issues.apache.org/jira/browse/MAPREDUCE-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-3078:
-----------------------------------------------
Attachment: MAPREDUCE-3078-20110927.txt
Attached patch should fix this. A summary of the changes:
- Setting and updating MR app progress as a function of progress of setup,
map, reduce and cleanup tasks.
- Using BuilderUtils to create records wherever necessary.
- Fixed the weird type hierarchy for RMCommunicator, RMContainerRequester and
RMContainerAllocator
- Reenabling TestRMContainerAllocator and adding a test for verifying
app-progress.
- SchedulerApp change: Reversed the order of steps to first update the
data-structures and then send out the event. Otherwise RMApp may poll for the
new container and can get null, this bug is uncovered by the test.
Tested this on a single node also, progress updates are showing up on the RM UI.
> Application's progress isn't updated from AM to RM.
> ---------------------------------------------------
>
> Key: MAPREDUCE-3078
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3078
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster, mrv2, resourcemanager
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-3078-20110927.txt
>
>
> It helps to be able to monitor the application-progress from the RM UI itself.
> Bits of it is already there, even the AM-RM API (in AllocateRequest). We just
> need to make sure the progress is produced and consumed properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
