You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2007/11/06 01:37:50 UTC
[jira] Commented: (HADOOP-2152) Data transfer buffer length in
DFSOutputStream should not be user controlled.
[ https://issues.apache.org/jira/browse/HADOOP-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540315 ]
Jim Kellerman commented on HADOOP-2152:
---------------------------------------
How does this issue relate to HADOOP-1707 which proposes elimination of client side caches?
In view of 1707, is this change still necessary?
> Data transfer buffer length in DFSOutputStream should not be user controlled.
> -----------------------------------------------------------------------------
>
> Key: HADOOP-2152
> URL: https://issues.apache.org/jira/browse/HADOOP-2152
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.14.0
> Reporter: Konstantin Shvachko
> Fix For: 0.16.0
>
>
> DFSOutputStream has two distinct buffers.
> First one is the user data buffer, which collects data the user writes into stream,
> and flushes it into a temporary local file when the buffer is full.
> Second is the data transfer buffer, which is used to transfer data from the client to a data-node.
> It turns out to be that both buffers have the same length defined by the user when the file is created.
> I think the two buffer lengths should be completely independent.
> The user data buffer can still be controlled by the user, but the data transfer
> buffer should have independent length optimized for better transfer rate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.