hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashikant Banerjee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-203) Add getCommittedBlockLength API in datanode
Date Wed, 25 Jul 2018 05:01:01 GMT

     [ https://issues.apache.org/jira/browse/HDDS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Shashikant Banerjee updated HDDS-203:
    Attachment: HDDS-203.06.patch

> Add getCommittedBlockLength API in datanode
> -------------------------------------------
>                 Key: HDDS-203
>                 URL: https://issues.apache.org/jira/browse/HDDS-203
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Client, Ozone Datanode
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>             Fix For: 0.2.1
>         Attachments: HDDS-203.00.patch, HDDS-203.01.patch, HDDS-203.02.patch, HDDS-203.03.patch,
HDDS-203.04.patch, HDDS-203.05.patch, HDDS-203.06.patch
> When a container gets closed on the Datanode while the active Writes are happening by
OzoneClient, Client Write requests will fail with ContainerClosedException. In such case,
ozone Client needs to enquire the last committed block length from dataNodes and update the
OzoneMaster with the updated length for the block. This Jira proposes to add to RPC call to
get the last committed length of a block on a Datanode.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message