hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7873) OIV webhdfs premature close channel issue
Date Wed, 11 Mar 2015 19:55:39 GMT

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

Haohui Mai commented on HDFS-7873:

Can you please format the code with the compliance of the Hadoop coding style:


I also don't understand why the unit test can effectively cover this issue. Can you explain?

> OIV webhdfs premature close channel issue
> -----------------------------------------
>                 Key: HDFS-7873
>                 URL: https://issues.apache.org/jira/browse/HDFS-7873
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 2.6.0, 2.5.2
>            Reporter: Benoit Perroud
>            Priority: Minor
>         Attachments: HDFS-7873-v1.txt, HDFS-7873-v2.txt
> The new Offline Image Viewer (OIV) supports to load the FSImage and _emulate_ a webhdfs
server to explore the image without touching the NN.
> This webhdfs server is not working with folders holding a significant number of children
(files or other folders):
> {quote}
> $  hadoop fs -ls webhdfs://
> 15/03/03 04:28:19 WARN ssl.FileBasedKeyStoresFactory: The property 'ssl.client.truststore.location'
has not been set, no TrustStore will be loaded
> 15/03/03 04:28:21 WARN security.UserGroupInformation: PriviledgedActionException as:bperroud
(auth:SIMPLE) cause:java.io.IOException: Response decoding failure: java.lang.IllegalStateException:
Expected one of '"}'
> ls: Response decoding failure: java.lang.IllegalStateException: Expected one of '"}'
> {quote}
> The error comes from an inappropriate usage of Netty. {{e.getFuture().addListener(ChannelFutureListener.CLOSE)}}
is closing the channel too early because the future attached to the channel already sent the
header so the I/O operation succeeded.

This message was sent by Atlassian JIRA

View raw message