[
https://issues.apache.org/jira/browse/MAPREDUCE-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated MAPREDUCE-2764:
-------------------------------------
Attachment: token-renew.patch
This patch fixes some of the remaining problems:
1. use a doAs for the job tracker when renewing and canceling tokens.
2. make the logging better.
3. fix some of the javadoc
4. protect against an npe when there is an unknown token type.
I've tested this with:
1. getting tokens via rpc and http from 204 to 205 and 205 to 204.
2. renewing and canceling tokens via rpc and http from 205 to 204.
3. getting/renewing/canceling tokens from 205 to 205.
4. run a distcp job in 205 with hftp ensuring both the hdfs and hftp tokens
are renewed and canceled.
5. using hftp from 204 and 205 to 204 and 205.
> Fix renewal of dfs delegation tokens
> ------------------------------------
>
> Key: MAPREDUCE-2764
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2764
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Daryn Sharp
> Assignee: Owen O'Malley
> Fix For: 0.20.205.0
>
> Attachments: MAPREDUCE-2764-2.patch, MAPREDUCE-2764-3.patch,
> MAPREDUCE-2764-4.patch, MAPREDUCE-2764.patch, delegation.patch,
> token-renew.patch, token-renew.patch
>
>
> The JT may have issues renewing hftp tokens which disrupt long distcp jobs.
> The problem is the JT's delegation token renewal code is built on brittle
> assumptions. The token's service field contains only the "ip:port" pair.
> The renewal process assumes that the scheme must be hdfs. If that fails due
> to a {{VersionMismatchException}}, it tries https based on another assumption
> that it must be hftp if it's not hdfs. A number of other exceptions, most
> commonly {{IOExceptions}}, can be generated which fouls up the renewal since
> it won't fallback to https.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
