[
https://issues.apache.org/jira/browse/HDFS-12626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Liang updated HDFS-12626:
------------------------------
Attachment: HDFS-12626-HDFS-7240.005.patch
Thanks [~xyao] for the review and the comments! All fixed in v005 patch except:
bq. Line 201: Do we update the keyInfo with the modification time when the
block is written to the container as well?
If I understand this question correctly. Then I believe writing a block to
container is a process between client and the containers, KSM is not involved
in this process so it does not know when a particular block write this done.
> Ozone : delete open key entries that will no longer be closed
> -------------------------------------------------------------
>
> Key: HDFS-12626
> URL: https://issues.apache.org/jira/browse/HDFS-12626
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chen Liang
> Assignee: Chen Liang
> Attachments: HDFS-12626-HDFS-7240.001.patch,
> HDFS-12626-HDFS-7240.002.patch, HDFS-12626-HDFS-7240.003.patch,
> HDFS-12626-HDFS-7240.004.patch, HDFS-12626-HDFS-7240.005.patch
>
>
> HDFS-12543 introduced the notion of "open key" where when a key is opened, an
> open key entry gets persisted, only after client calls a close will this
> entry be made visible. One issue is that if the client does not call close
> (e.g. failed), then that open key entry will never be deleted from meta data.
> This JIRA tracks this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
