[ 
https://issues.apache.org/jira/browse/MAPREDUCE-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922532#comment-16922532
 ] 

Hadoop QA commented on MAPREDUCE-7227:
--------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  7s{color} 
| {color:red} MAPREDUCE-7227 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | MAPREDUCE-7227 |
| Console output | 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7661/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> 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, HADOOP-MAPREDUCE-7227.005.patch, 
> Process_Analysis.png
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to