You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Shashikant Banerjee (JIRA)" <ji...@apache.org> on 2018/08/10 08:35:00 UTC
[jira] [Resolved] (HDDS-322) Restructure ChunkGroupOutputStream and
ChunkOutputStream
[ https://issues.apache.org/jira/browse/HDDS-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shashikant Banerjee resolved HDDS-322.
--------------------------------------
Resolution: Won't Do
> Restructure ChunkGroupOutputStream and ChunkOutputStream
> --------------------------------------------------------
>
> Key: HDDS-322
> URL: https://issues.apache.org/jira/browse/HDDS-322
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Client
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 0.2.1
>
>
> Currently, ChunkOutputStream allocate a chunk size buffer to cache client data. The idea here is to allocate the buffer in ChunkGroupOutputStream and pass it to underlying ChunkOutputStream so as to make reclaiming of the uncommitted leftover data in the buffer and reallocating to next Block while handling CLOSE_CONTAINER_EXCEPTION in ozone client becomes simpler. This Jira will also add the code to close the underlying ChunkOutputStream as soon as the complete block data is written.
> This Jira will also modify the PutKey response to contain the committed block length to ozone client to do some validation checks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org