[
https://issues.apache.org/jira/browse/HDFS-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571341#comment-14571341
]
Krish Dey commented on HDFS-6600:
---------------------------------
HI Chris Nauroth,
I think I have tried using UserGroupInformation.getLoginUser().doAs(...) but
will try that once more and let you know.
Will revert the clean up/formatting on the classes and resubmit it.
I agree on the thought of using private API and associates the block to new
path/Inode
Thanks
Krish
> fsck -move fails in secured clusters.
> -------------------------------------
>
> Key: HDFS-6600
> URL: https://issues.apache.org/jira/browse/HDFS-6600
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: security, tools
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Chris Nauroth
> Assignee: Krish Dey
> Labels: BB2015-05-TBR
> Attachments: HDFS-6600.1.PATCH
>
>
> In a secured cluster, running hdfs fsck -move fails. When trying to move the
> recovered blocks to lost+found, fsck tries to start using a DFSClient, but it
> doesn't have the credentials to authenticate that client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)