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/11 08:26:00 UTC
[jira] [Updated] (HDDS-246) Datanode should throw
BlockNotCommittedException for uncommitted blocks to Ozone Client
[ https://issues.apache.org/jira/browse/HDDS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shashikant Banerjee updated HDDS-246:
-------------------------------------
Summary: Datanode should throw BlockNotCommittedException for uncommitted blocks to Ozone Client (was: Ratis leader should throw BlockNotCommittedException for uncommitted blocks to Ozone Client)
> Datanode should throw BlockNotCommittedException for uncommitted blocks to Ozone Client
> ---------------------------------------------------------------------------------------
>
> Key: HDDS-246
> URL: https://issues.apache.org/jira/browse/HDDS-246
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 0.2.1
>
>
> As a part of closing the container on a datanode, all the open keys(blocks) will be committed.In between if the client calls getCommittedBlockLength for uncommitted block on the container, the leader will throw BlockNotCommitted exception to the Client Back. The client should retry to fetch the committed block length and update the OzoneManager with the length.
>
--
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