You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Shashikant Banerjee (JIRA)" <ji...@apache.org> on 2018/07/21 10:19:00 UTC
[jira] [Commented] (HDDS-247) Handle CLOSED_CONTAINER_IO exception
in ozoneClient
[ https://issues.apache.org/jira/browse/HDDS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551607#comment-16551607 ]
Shashikant Banerjee commented on HDDS-247:
------------------------------------------
patch v0 is dependent on HDDS-226 and HDDS-203. Not submitting it for now.
> Handle CLOSED_CONTAINER_IO exception in ozoneClient
> ---------------------------------------------------
>
> Key: HDDS-247
> URL: https://issues.apache.org/jira/browse/HDDS-247
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Client
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-247.00.patch
>
>
> In case of ongoing writes by Ozone client to a container, the container might get closed on the Datanodes because of node loss, out of space issues etc. In such cases, the operation will fail with CLOSED_CONTAINER_IO exception. In cases as such, ozone client should try to get the committed length of the block from the Datanodes, and update the KSM. This Jira aims to address this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org