[HADOOP-6632] Support for using different Kerberos keys for different instances of Hadoop services - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 0.22.0
Component/s: None
Labels:
None

Description

We tested using the same Kerberos key for all datanodes in a HDFS cluster or the same Kerberos key for all TaskTarckers in a MapRed cluster. But it doesn't work. The reason is that when datanodes try to authenticate to the namenode all at once, the Kerberos authenticators they send to the namenode may have the same timestamp and will be rejected as replay requests. This JIRA makes it possible to use a unique key for each service instance.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HADOOP-6632-Y20S-18.patch
14/Mar/10 04:47
40 kB
Kan Zhang
HADOOP-6632-Y20S-22.patch
18/Mar/10 10:50
47 kB
Jitendra Nath Pandey
6632.mr.patch
19/Mar/10 18:14
2 kB
Devaraj Das
c6632-05.patch
15/Jul/10 17:40
19 kB
Kan Zhang
c6632-07.patch
19/Jul/10 23:15
19 kB
Kan Zhang

Issue Links

blocks

HDFS-1201 Support for using different Kerberos keys for Namenode and datanode.

Closed

incorporates

MAPREDUCE-1945 Support for using different Kerberos keys for Jobtracker and TaskTrackers

Closed

Activity

People

Assignee:: Kan Zhang

Reporter:: Kan Zhang

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 14/Mar/10 04:28

Updated:: 12/Dec/11 06:19

Resolved:: 20/Jul/10 00:51