[ https://issues.apache.org/jira/browse/FLINK-22534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junfan Zhang updated FLINK-22534: --------------------------------- Attachment: debug2.PNG > Set delegation token's service name as credential alias > ------------------------------------------------------- > > Key: FLINK-22534 > URL: https://issues.apache.org/jira/browse/FLINK-22534 > Project: Flink > Issue Type: Improvement > Components: Connectors / Hadoop Compatibility > Reporter: Junfan Zhang > Assignee: Junfan Zhang > Priority: Major > Labels: pull-request-available > Attachments: debug2.PNG > > > h4. What > Set the Hadoop delegation token's service name as credential alias. > h4. Why > In current implementation, Flink will use delegation token's service name or > identifer as credential alias, refer to Flink code HadoopModule and Yarn > Utils. > Firstly, I think we could use the same way to set credential alias, like > delegation token's service name. It will be more clear. > Secondly, when fetching HDFS delegation token and then inject all tokens to > current UserGroupInformation in Hadoop HDFS federation mode, it will cause > the problem of overwriting the different delegation tokens with the same > identifier, refer to code here. > h5. When does the same identifier delegation tokens appear? > Hadoop HA delegation tokens will have the same identifier(Refer to > [HDFS-9276|https://issues.apache.org/jira/browse/HDFS-9276]), but its' > service name is different. So we can use service name as alias. > The following figure from > [HDFS-9276|https://issues.apache.org/jira/browse/HDFS-9276] can show that the > identifier of HA delegation token is the same. -- This message was sent by Atlassian Jira (v8.3.4#803005)