Details
Description
We have observed that an HDFS delegation token fetched by a 2.3.0 client cannot be used by a 2.6.1 client, and vice versa. Through some debugging I found that it's a mismatch between the token's service and the service of the filesystem (e.g. webhdfs://host.something.com:50070/). One would be in numerical IP address and one would be in non-numerical hostname format.
Attachments
Attachments
Issue Links
- is related to
-
MAPREDUCE-6565 Configuration to use host name in delegation token service is not read from job.xml during MapReduce job execution.
- Resolved
- relates to
-
HADOOP-7733 Mapreduce jobs are failing when JT has hadoop.security.token.service.use_ip=false and client has hadoop.security.token.service.use_ip=true
- Resolved