hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-246) Datanode should throw BlockNotCommittedException for uncommitted blocks to Ozone Client
Date Wed, 25 Jul 2018 21:27:00 GMT

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

Jitendra Nath Pandey updated HDDS-246:
--------------------------------------
    Priority: Blocker  (was: Major)

> 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: Blocker
>             Fix For: 0.2.1
>
>         Attachments: HDDS-246.00.patch
>
>
> 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


Mime
View raw message