[ 
https://issues.apache.org/jira/browse/HADOOP-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649553#action_12649553
 ] 

dhruba borthakur commented on HADOOP-4616:
------------------------------------------

This patch introduces a debug print into stderr in libhdfs:

+            if (noReadBytes == 0 || noReadBytes < -1) {
+              fprintf(stderr, "WARN: FSDataInputStream.read returned invalid 
return code - libhdfs returning EOF, i.e., 0: %d\n", noReadBytes);
+            }

I am fine with it but would like to poll the user-community to see if this 
could break any application that is currently using libhdfs.

> assertion makes fuse-dfs exit when reading incomplete data
> ----------------------------------------------------------
>
>                 Key: HADOOP-4616
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4616
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/fuse-dfs
>    Affects Versions: 0.18.2
>            Reporter: Marc-Olivier Fleury
>            Assignee: Pete Wyckoff
>            Priority: Blocker
>             Fix For: 0.18.3, 0.19.1, 0.20.0
>
>         Attachments: HADOOP-4616.txt, HADOOP-4616.txt, HADOOP-4616.txt, 
> HADOOP-4616_0.18.2.txt, HADOOP-4616_0.18.2.txt, HADOOP-4616_0.19.txt, 
> HADOOP-4616_0.19.txt
>
>
> When trying to read a file that is corrupt on HDFS (registered by the 
> namenode, but part of the data is missing on the datanodes), some of the 
> assertions in dfs_read fail, causing the program to abort. This makes it  
> impossible to access the mounted partition until it is mounted again.
> A simple way to reproduce this bug is to remove enough datanodes to have part 
> of the data missing, and to read each file listed in HDFS.
> this is the assertion that fails (fuse_dfs.c:903) : assert(bufferReadIndex >= 
> 0 && bufferReadIndex < fh->bufferSize);
> The expected behaviour would be to return either no file or a corrupt file, 
> but continue working afterward.
> removing the assertion seems to work for now, but a special behaviour is 
> probably needed to handle this particular problem correctly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to