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 92E44D20F for ; Sun, 2 Dec 2012 04:44:02 +0000 (UTC) Received: (qmail 59982 invoked by uid 500); 2 Dec 2012 04:44:01 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 59090 invoked by uid 500); 2 Dec 2012 04:44:00 -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 59038 invoked by uid 99); 2 Dec 2012 04:43:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2012 04:43:59 +0000 Date: Sun, 2 Dec 2012 04:43:59 +0000 (UTC) From: "Harsh J (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <2140554058.50240.1354423439657.JavaMail.jiratomcat@arcas> In-Reply-To: <1250000856.50233.1354423198781.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (HDFS-4259) Improve pipeline DN replacement failure message 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-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-4259: -------------------------- Status: Patch Available (was: Open) > Improve pipeline DN replacement failure message > ----------------------------------------------- > > Key: HDFS-4259 > URL: https://issues.apache.org/jira/browse/HDFS-4259 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs-client > Affects Versions: 2.0.2-alpha > Reporter: Harsh J > Assignee: Harsh J > Priority: Minor > Attachments: HDFS-4259.patch > > > The current message shown is something such as below: > bq. Failed to add a datanode. User may turn off this feature by setting X.policy in configuration, where the current policy is Y. (Nodes: current=\[foo\], original=\[bar\]) > This reads off like failing is a feature (but the intention and the reason we hit this isn't indicated strongly), and can be bettered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira