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 "Lokesh Jain (JIRA)" <ji...@apache.org> on 2018/06/06 08:48:00 UTC
[jira] [Commented] (HDDS-72) Add deleteTransactionId field in
ContainerInfo
[ https://issues.apache.org/jira/browse/HDDS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503006#comment-16503006 ]
Lokesh Jain commented on HDDS-72:
---------------------------------
[~xyao] Thanks for reviewing the patch! I have updated MetadataKeyFilters.java to include multiple filters in the v4 patch. The deleteTransactionID field is required to identify garbage in the system. The deleteBlockLog would be purged based on size limit or time duration of the entries. After purge there is no reliable source for the SCM to know what state a container is in. That is what brought the concept of deleteTransactionId.
> Add deleteTransactionId field in ContainerInfo
> ----------------------------------------------
>
> Key: HDDS-72
> URL: https://issues.apache.org/jira/browse/HDDS-72
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode, SCM
> Affects Versions: 0.2.1
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-72.001.patch, HDDS-72.002.patch, HDDS-72.003.patch, HDDS-72.004.patch
>
>
> This Jira aims to add deleteTransactionId field in SCMContainerInfo and ContainerInfo in hdds.proto and StorageContainerDatanodeProtocol.proto respectively. This transactionId would be used to maintain the state of container w.r.t deleted blocks and would be used by SCM to delete unwanted blocks in DN.
--
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