[YARN-4126] RM should not issue delegation tokens in unsecure mode - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.0.0-alpha1
Component/s: None
Labels:
None

Hadoop Flags:

Incompatible change, Reviewed
Release Note:
Yarn now only issues and allows delegation tokens in secure clusters. Clients should no longer request delegation tokens in a non-secure cluster, or they'll receive an IOException.

Description

ClientRMService#getDelegationToken is currently returning a delegation token in insecure mode. We should not return the token if it's in insecure mode.

Attachments

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

0001-YARN-4126.patch
08/Sep/15 06:12
1.0 kB
Bibin Chundatt
0002-YARN-4126.patch
08/Sep/15 06:32
2 kB
Bibin Chundatt
0003-YARN-4126.patch
08/Sep/15 19:33
11 kB
Bibin Chundatt
0004-YARN-4126.patch
09/Sep/15 02:23
13 kB
Bibin Chundatt
0005-YARN-4126.patch
09/Sep/15 08:43
14 kB
Bibin Chundatt
0006-YARN-4126.patch
11/Sep/15 15:32
31 kB
Bibin Chundatt

Issue Links

blocks

YARN-5882 Test only changes from YARN-4126

Resolved

breaks

MAPREDUCE-6508 TestNetworkedJob fails consistently due to delegation token changes on RM.

Resolved

YARN-5750 YARN-4126 broke Oozie on unsecure cluster

Resolved

Activity

People

Assignee:: Bibin Chundatt

Reporter:: Jian He

Votes:: 0 Vote for this issue

Watchers:: 16 Start watching this issue

Dates

Created:: 08/Sep/15 05:37

Updated:: 15/Dec/16 19:52

Resolved:: 14/Sep/15 06:16