[ https://issues.apache.org/jira/browse/MAPREDUCE-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915804#comment-16915804 ]
Zhankun Tang edited comment on MAPREDUCE-7227 at 8/26/19 2:04 PM: ------------------------------------------------------------------ Bulk update: Preparing for 3.1.3 release. moved all legacy 3.1.2 non-blocker issues to 3.1.4, please move back if it is a blocker for you. was (Author: tangzhankun): Bulk update: Preparing for 3.1.3 release. moved all 3.1.2 non-blocker issues to 3.1.4, please move back if it is a blocker for you. > Fix job staging directory residual problem in a big yarn cluster composed of > multiple independent hdfs clusters > --------------------------------------------------------------------------------------------------------------- > > Key: MAPREDUCE-7227 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7227 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster, mrv2 > Affects Versions: 2.6.0, 2.7.0, 3.1.2 > Reporter: Yuan LUO > Assignee: Yuan LUO > Priority: Major > Attachments: 1.png, 2.png, HADOOP-MAPREDUCE-7227.001.patch, > HADOOP-MAPREDUCE-7227.002.patch, HADOOP-MAPREDUCE-7227.003.patch, > HADOOP-MAPREDUCE-7227.004.patch > > > Our yarn cluster is made up of some independent hdfs cluster, the > 'default.FS' in every hdfs cluster is different.when user submit job to yarn > cluster, if the 'default.FS' between client and nodemanager is > inconsistent, then the job staging dir can't be cleanup by AppMaster. Because > it will produce two job staging dirs in our conditions by client and > appmaster. So we can modify AppMaster through client's ‘default.FS’ to > create job staging dir. -- This message was sent by Atlassian Jira (v8.3.2#803003) --------------------------------------------------------------------- To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org