Return-Path: 
 <hdfs-issues-return-79528-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 09102105BE
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Fri, 21 Feb 2014 23:56:45 +0000 (UTC)
Received: (qmail 24436 invoked by uid 500); 21 Feb 2014 23:55:19 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 23828 invoked by uid 500); 21 Feb 2014 23:54:58 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 23592 invoked by uid 99); 21 Feb 2014 23:54:20 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Feb 2014 23:54:20 +0000
Date: Fri, 21 Feb 2014 23:54:20 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12694820.1392233726277.84591.1393026860127@arcas>
In-Reply-To: <JIRA.12694820.1392233726277@arcas>
References: <JIRA.12694820.1392233726277@arcas>
Subject: [jira] [Commented] (HDFS-5939) WebHdfs returns misleading error
 code and logs nothing if trying to create a file with no DNs in cluster
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-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909003#comment-13909003 ] 

Aaron T. Myers commented on HDFS-5939:
--------------------------------------

bq. On the other hand, I wonder if it's a bug that the system set the replication to 0 (instead of non-zero), and we now have to manually set the replication to non-zero?

I wouldn't consider it a bug necessarily, but really just a quirk of the way MiniDFSCluster works currently. I personally would recommend against changing it, since there are probably other tests that either deliberately or inadvertently rely on the current behavior, and you might break them were you to change it.

> WebHdfs returns misleading error code and logs nothing if trying to create a file with no DNs in cluster
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-5939
>                 URL: https://issues.apache.org/jira/browse/HDFS-5939
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>    Affects Versions: 2.3.0
>            Reporter: Yongjun Zhang
>            Assignee: Yongjun Zhang
>         Attachments: HDFS-5939.001.patch, HDFS-5939.002.patch, HDFS-5939.003.patch, HDFS-5939.004.patch
>
>
> When trying to access hdfs via webhdfs, and when datanode is dead, user will see an exception below without any clue that it's caused by dead datanode:
> $ curl -i -X PUT ".../webhdfs/v1/t1?op=CREATE&user.name=<userName>&overwrite=false"
> ...
> {"RemoteException":{"exception":"IllegalArgumentException","javaClassName":"java.lang.IllegalArgumentException","message":"n must be positive"}}
> Need to fix the report to give user hint about dead datanode.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)