hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lokesh Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-178) DN should update transactionId on block delete
Date Thu, 28 Jun 2018 07:18:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526013#comment-16526013
] 

Lokesh Jain commented on HDDS-178:
----------------------------------

[~xyao] I have removed the changes related to avoiding block deletes in open containers in the
v5 patch. I have also updated the title and description to reflect the same. I will open up
a separate Jira for handling block deletes in open containers.

> DN should update transactionId on block delete
> ----------------------------------------------
>
>                 Key: HDDS-178
>                 URL: https://issues.apache.org/jira/browse/HDDS-178
>             Project: Hadoop Distributed Data Store
>          Issue Type: Task
>          Components: Ozone Datanode
>            Reporter: Lokesh Jain
>            Assignee: Lokesh Jain
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-178.001.patch, HDDS-178.002.patch, HDDS-178.003.patch, HDDS-178.004.patch,
HDDS-178.005.patch
>
>
> Currently datanode does not update delete transactionId on block deletes. This Jira
aims to update the containerData for the containers on block deletes.



--
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