Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 12 May 2011 16:33:47 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1685518414.7221.1305218027398.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1176966401.11904.1301078529898.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1787) "Not enough xcievers" error should
 propagate to client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032495#comment-13032495 ] 

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

You're encouraged to look at the test failures, but I'm pretty confident they're unrelated to this patch. Those tests are known to be failing on trunk.

> "Not enough xcievers" error should propagate to client
> ------------------------------------------------------
>
>                 Key: HDFS-1787
>                 URL: https://issues.apache.org/jira/browse/HDFS-1787
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Todd Lipcon
>            Assignee: Jonathan Hsieh
>              Labels: newbie
>         Attachments: hdfs-1787.patch
>
>
> We find that users often run into the default transceiver limits in the DN. Putting aside the inherent issues with xceiver threads, it would be nice if the "xceiver limit exceeded" error propagated to the client. Currently, clients simply see an EOFException which is hard to interpret, and have to go slogging through DN logs to find the underlying issue.
> The data transfer protocol should be extended to either have a special error code for "not enough xceivers" or should have some error code for generic errors with which a string can be attached and propagated.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira