Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DFA1B110AA for ; Tue, 24 Jun 2014 19:20:26 +0000 (UTC) Received: (qmail 3439 invoked by uid 500); 24 Jun 2014 19:20:25 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 3355 invoked by uid 500); 24 Jun 2014 19:20:25 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 3119 invoked by uid 99); 24 Jun 2014 19:20:25 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jun 2014 19:20:25 +0000 Date: Tue, 24 Jun 2014 19:20:25 +0000 (UTC) From: "Chris Nauroth (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-6600) fsck -move fails in secured clusters. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-6600: -------------------------------- Component/s: security > 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 > > 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.2#6252)