[jira] [Resolved] (MAPREDUCE-5298) Move MapReduce services to YARN-117 stricter lifecycle
[ https://issues.apache.org/jira/browse/MAPREDUCE-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-5298. Resolution: Fixed Fix Version/s: 2.1.0-beta Hadoop Flags: Reviewed Committed this to trunk, branch-2 and branch-2.1 along with YARN-117/YARN-530. Closing this. Move MapReduce services to YARN-117 stricter lifecycle -- Key: MAPREDUCE-5298 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5298 Project: Hadoop Map/Reduce Issue Type: New Feature Components: applicationmaster Affects Versions: 2.0.4-alpha Reporter: Steve Loughran Assignee: Steve Loughran Fix For: 2.1.0-beta Attachments: MAPREDUCE-5298-016.patch, MAPREDUCE-5298-018.patch, MAPREDUCE-5298-019.patch, MAPREDUCE-5298-020.patch, MAPREDUCE-5298-021.patch, MAPREDUCE-5298-022.patch, MAPREDUCE-5298-023.patch The MR services need to be in sync with the YARN-117 lifecycle enhancements -- 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
[jira] [Created] (MAPREDUCE-5321) Enable better parallelism in the Fair Scheduler
Sandy Ryza created MAPREDUCE-5321: - Summary: Enable better parallelism in the Fair Scheduler Key: MAPREDUCE-5321 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5321 Project: Hadoop Map/Reduce Issue Type: Improvement Reporter: Sandy Ryza Assignee: Sandy Ryza Currently, the Fair Scheduler is locked on pretty much every operation, node updates, application additions and removals, every time the update thread runs, and every time the RM queries it for information. Most of this locking is unnecessary, especially as only the core scheduling operations like application additions, removals, and node updates need a consistent view of scheduler state. We can probably increase parallelism by using concurrent data structures when applicable, as well as keeping a slightly stale view to serve via the RM APIs. -- 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
[jira] [Resolved] (MAPREDUCE-4069) Cleanup task tokens interface
[ https://issues.apache.org/jira/browse/MAPREDUCE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-4069. Resolution: Duplicate Fixed by MAPREDUCE-5199. Cleanup task tokens interface - Key: MAPREDUCE-4069 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4069 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.2 Reporter: Jason Lowe Priority: Minor This tracks a couple of cleanup issues that were identified in MAPREDUCE-4043: * It seems unnecessary to pass the job token and credentials separately when we always combine the job token into the credentials before building the container launch context. The TaskImpl and TaskAttemptImpl constructors could simply take credentials with the job token already added rather than separate job token and credential parameters. * It's unclear whether we still need the appTokens file that is placed into HDFS by the job submitter, localized by the NM, and finally read in by the AM. I believe the AM's credentials sent in the AM's container launch context already contains the same information. If that's the case, we should remove the code related to the appTokens file. -- 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
[jira] [Created] (MAPREDUCE-5322) If input path does not exist application/job id is getting assigned.
Nishan Shetty created MAPREDUCE-5322: Summary: If input path does not exist application/job id is getting assigned. Key: MAPREDUCE-5322 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5322 Project: Hadoop Map/Reduce Issue Type: Bug Components: resourcemanager Affects Versions: 2.0.2-alpha, 2.0.1-alpha Reporter: Nishan Shetty Priority: Minor 1.Run job by giving input as some path which does not exist 2.Application/job is is getting assigned. 2013-06-12 16:00:24,494 INFO org.apache.hadoop.yarn.server.resourcemanager.ClientRMService: Allocated new applicationId: 12 Suggestion Before assiging job/app id input path check can be made. -- 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
