[
https://issues.apache.org/jira/browse/HAWQ-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193943#comment-15193943
]
Jemish Patel commented on HAWQ-482:
-----------------------------------
What I see happening is the user postgres@{REALM} requests a delegation token
from NN (isilon in this case) and gets a token for hdfs@{REALM}.
Then when postgres tries to cancel, he is not the owner of that token (as it is
for hdfs@{REALM} ) and hence there is an error as the owner would be hdfs and
not postgres. Correct?
If that is correct, than this warning would be thrown even on a non-Isilon
environment.
Let me know.
Jemish
> Failed to cancel HDFS delegation token
> --------------------------------------
>
> Key: HAWQ-482
> URL: https://issues.apache.org/jira/browse/HAWQ-482
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Security
> Affects Versions: 2.0.0-beta-incubating
> Reporter: Jemish Patel
> Assignee: Lei Chang
> Attachments: hawq-2016-03-03_000000.csv, hdfs.log
>
>
> Hi I am using HDB 2.0.0.0_beta-19716 in a kerberized environment.
> Every time I select/insert rows or create a table, I see the warning below:
> WARNING: failed to cancel hdfs delegation token.
> DETAIL: User postg...@vlan172.fe.gopivotal.com is not authorized to cancel
> the token
> The operation does succeed but I am wondering why is it trying to delete a
> delegation token and if I have something misconfigured?
> Can you please let me know why this is happening and how to resolve it?
> Jemish
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
