[
https://issues.apache.org/jira/browse/HDFS-7694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308729#comment-14308729
]
stack commented on HDFS-7694:
-----------------------------
CanUnbuffer ain't too pretty. Unbufferable is about as ugly. Its fine I
suppose as is.
In DFSIS#unbuffer, should we be resetting data members back to zero, etc?
In testOpenManyFilesViaTcp, we assert we can read but is there a reason why we
would not be able to that unbuffer enables? (pardon if dumb question)
> FSDataInputStream should support "unbuffer"
> -------------------------------------------
>
> Key: HDFS-7694
> URL: https://issues.apache.org/jira/browse/HDFS-7694
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.7.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-7694.001.patch, HDFS-7694.002.patch
>
>
> For applications that have many open HDFS (or other Hadoop filesystem) files,
> it would be useful to have an API to clear readahead buffers and sockets.
> This could be added to the existing APIs as an optional interface, in much
> the same way as we added setReadahead / setDropBehind / etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
