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

Hudson commented on MAPREDUCE-6285:
-----------------------------------

SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2093 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2093/])
MAPREDUCE-6285. ClientServiceDelegate should not retry upon 
AuthenticationException. Contributed by Jonathan Eagles. (ozawa: rev 
4170c99147b0cb6d561ff626cea140e0a061b314)
* hadoop-mapreduce-project/CHANGES.txt
* 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/ClientServiceDelegate.java
* 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/TestClientServiceDelegate.java


> ClientServiceDelegate should not retry upon AuthenticationException
> -------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6285
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6285
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Jonathan Eagles
>            Assignee: Jonathan Eagles
>             Fix For: 2.7.0
>
>         Attachments: MAPREDUCE-6285.1.patch, MAPREDUCE-6285.2.patch, 
> MAPREDUCE-6285.2.patch
>
>
> ClientServiceDelegate tries really hard to getJobStatus from a job through 
> retries. However, if an AuthorizationException occurs, it will always 
> continue to fail no matter how many retries it makes. AuthorizationException 
> is also thrown when mapred job -status is call on unsupported services like 
> tez jobs. This jira will limit the negative effect on AMs in both scenarios.
> Caused by: 
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.authorize.AuthorizationException):
>  Protocol interface org.apache.hadoop.mapreduce.v2.api.MRClientProtocolPB is 
> not known.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to