Return-Path: <hdfs-dev-return-25876-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 33E2B2009F8
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Fri,  3 Jun 2016 16:46:01 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 32B66160A55; Fri,  3 Jun 2016 14:46:01 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 7A426160A3B
	for <archive-asf-public@cust-asf.ponee.io>; Fri,  3 Jun 2016 16:46:00 +0200 (CEST)
Received: (qmail 16814 invoked by uid 500); 3 Jun 2016 14:45:59 -0000
Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-dev@hadoop.apache.org>
List-Id: <hdfs-dev.hadoop.apache.org>
Delivered-To: mailing list hdfs-dev@hadoop.apache.org
Received: (qmail 16792 invoked by uid 99); 3 Jun 2016 14:45:59 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jun 2016 14:45:59 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 449252C1F5A
	for <hdfs-dev@hadoop.apache.org>; Fri,  3 Jun 2016 14:45:59 +0000 (UTC)
Date: Fri, 3 Jun 2016 14:45:59 +0000 (UTC)
From: "pt (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12975505.1464965103000.25632.1464965159277@Atlassian.JIRA>
In-Reply-To: <JIRA.12975505.1464965103000@Atlassian.JIRA>
References: <JIRA.12975505.1464965103000@Atlassian.JIRA> <JIRA.12975505.1464965103224@arcas>
Subject: [jira] [Created] (HDFS-10484) Can not read file from
 java.io.IOException: Need XXX bytes, but only YYY  bytes available
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Fri, 03 Jun 2016 14:46:01 -0000

pt created HDFS-10484:
-------------------------

             Summary: Can not read file from java.io.IOException: Need XXX bytes, but only YYY  bytes available
                 Key: HDFS-10484
                 URL: https://issues.apache.org/jira/browse/HDFS-10484
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: hdfs
    Affects Versions: 2.0.0-alpha
         Environment: Cloudera 4.1.2,  hadoop-hdfs-2.0.0+552-1.cdh4.1.2.p0.27
            Reporter: pt


We are running CDH 4.1.2 distro and trying to read file from HDFS. It ends up with exception @datanode saying


2016-06-02 10:43:26,354 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: DatanodeRegistration(X.X.X.X, storageID=DS-404876644-X.X.X.X-50010-1462535537579, infoPort=50075, ipcPort=50020, storageInfo=lv=-40;cid=cluster18;nsid=2115086255;c=0):Got exception while serving BP-2091182050-X.X.X.X-1358362115729:blk_5037101550399368941_420502314 to /X.X.X.X:58614
java.io.IOException: Need 10172416 bytes, but only 10072576 bytes available
at org.apache.hadoop.hdfs.server.datanode.BlockSender.waitForMinLength(BlockSender.java:387)
at org.apache.hadoop.hdfs.server.datanode.BlockSender.<init>(BlockSender.java:189)
at org.apache.hadoop.hdfs.server.datanode.DataXceiver.readBlock(DataXceiver.java:268)
at org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.opReadBlock(Receiver.java:88)
at org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.processOp(Receiver.java:63)
at org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:219)
at java.lang.Thread.run(Thread.java:662)
2016-06-02 10:43:26,354 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: app112.rutarget.ru:50010:DataXceiver error processing READ_BLOCK operation src: /X.X.X.X:58614 dest: /X.X.X.X:50010
java.io.IOException: Need 10172416 bytes, but only 10072576 bytes available
at org.apache.hadoop.hdfs.server.datanode.BlockSender.waitForMinLength(BlockSender.java:387)
at org.apache.hadoop.hdfs.server.datanode.BlockSender.<init>(BlockSender.java:189)
at org.apache.hadoop.hdfs.server.datanode.DataXceiver.readBlock(DataXceiver.java:268)
at org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.opReadBlock(Receiver.java:88)
at org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.processOp(Receiver.java:63)
at org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:219)
at java.lang.Thread.run(Thread.java:662)



FSCK shows file as being open for write, however hdfs client that handles writes to this file closed it long time ago -- so file stucked in RBW for a few last days. How can we get actual data  block in this case? I found only binary .meta file on datanode but not actual block with data.



-- 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org