You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/05/08 20:09:02 UTC
[jira] [Resolved] (MAPREDUCE-5567) [Umbrella] Stabilize MR
framework w.r.t ResourceManager restart
[ https://issues.apache.org/jira/browse/MAPREDUCE-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5567.
------------------------------------------------
Resolution: Fixed
Resolving this umbrella JIRA. RM restart has largely been nearly complete/stable in YARN, with MR working equally well in tandem since this ticket was opened, what with its ultimate usage for rolling-upgrades (YARN-666).
- As new issues come in, we can open new tickets.
- Will leave the one open sub-task as it is.
- No fix-version as this was done across releases.
> [Umbrella] Stabilize MR framework w.r.t ResourceManager restart
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-5567
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5567
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
>
> There are a bunch of tickets tracking MR AM's issues w.r.t RM restart. Consolidating them here so that we don't make contradictory fixes accross JIRAs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)