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 7368610290 for ; Mon, 7 Sep 2015 05:21:46 +0000 (UTC) Received: (qmail 92173 invoked by uid 500); 7 Sep 2015 05:21:46 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 92115 invoked by uid 500); 7 Sep 2015 05:21:46 -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 92098 invoked by uid 99); 7 Sep 2015 05:21:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Sep 2015 05:21:46 +0000 Date: Mon, 7 Sep 2015 05:21:46 +0000 (UTC) From: "Harsh J (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-7899) Improve EOF error 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-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733250#comment-14733250 ] Harsh J commented on HDFS-7899: ------------------------------- Thanks Jagadesh, that message change was just a small idea to make it carry slightly more sense. Do you have any ideas also to improve the situation such that users may be able to self-figure out whats going on? I've seen this appear during socket disconnects/timeouts/etc. - but the message it prints is from the software layer instead, which causes confusion. > Improve EOF error message > ------------------------- > > Key: HDFS-7899 > URL: https://issues.apache.org/jira/browse/HDFS-7899 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs-client > Affects Versions: 2.6.0 > Reporter: Harsh J > Assignee: Jagadesh Kiran N > Priority: Minor > Attachments: HDFS-7899-00.patch > > > Currently, a DN disconnection for reasons other than connection timeout or refused messages, such as an EOF message as a result of rejection or other network fault, reports in this manner: > {code} > WARN org.apache.hadoop.hdfs.DFSClient: Failed to connect to /x.x.x.x:nnnn for block, add to deadNodes and continue. java.io.EOFException: Premature EOF: no length prefix available > java.io.EOFException: Premature EOF: no length prefix available > at org.apache.hadoop.hdfs.protocol.HdfsProtoUtil.vintPrefixed(HdfsProtoUtil.java:171) > at org.apache.hadoop.hdfs.RemoteBlockReader2.newBlockReader(RemoteBlockReader2.java:392) > at org.apache.hadoop.hdfs.BlockReaderFactory.newBlockReader(BlockReaderFactory.java:137) > at org.apache.hadoop.hdfs.DFSInputStream.getBlockReader(DFSInputStream.java:1103) > at org.apache.hadoop.hdfs.DFSInputStream.blockSeekTo(DFSInputStream.java:538) > at org.apache.hadoop.hdfs.DFSInputStream.readWithStrategy(DFSInputStream.java:750) > at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:794) > at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:602) > {code} > This is not very clear to a user (warn's at the hdfs-client). It could likely be improved with a more diagnosable message, or at least the direct reason than an EOF. -- This message was sent by Atlassian JIRA (v6.3.4#6332)