[
https://issues.apache.org/jira/browse/HDFS-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154259#comment-16154259
]
Nandakumar commented on HDFS-12235:
-----------------------------------
Thanks [~yuanbo] & [~cheersyang] for working on this.
*KeySpaceManager*
> Should we have metadataManager.start() inside KeyManager#start()? since
> metadataManager is shared among VolumeManager, BucketManager and KeyManager
> it's better to retain start and stop of MetadataManager in KeySpaceManager
> itself.
*KeyDeletingService#KeyDeletingTask*
> If DeleteKeyBlocksResult#isSuccess returns false, we should log it in KSM.
> Since the there is some problem in deleting the key.
With {{DeleteKeyBlocksResult}} and {{KsmKeyBlocks}} in
{{StorageContainerManager#deleteKeyBlocks}} call now SCM is aware of KSM and
knows the key to block mapping, which SCM doesn't have to know.
{{StorageContainerManager#deleteKeyBlocks}} will become KSM specific API in
SCM, other clients (any application) if they want to use block service of SCM,
either the application has to use KSM's format of key-block mapping or we have
to introduce a generic delete block API call in SCM.
Will making a new RPC call to SCM for each key delete be too much overhead?
With this we can avoid sending key information to SCM and the delete API call
will be generic so that any client can use it. This will also make block
service of SCM work only at block level and not to worry about any high level
grouping of blocks.
> Ozone: DeleteKey-3: KSM SCM block deletion message and ACK interactions
> -----------------------------------------------------------------------
>
> Key: HDFS-12235
> URL: https://issues.apache.org/jira/browse/HDFS-12235
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Attachments: HDFS-12235-HDFS-7240.001.patch,
> HDFS-12235-HDFS-7240.002.patch, HDFS-12235-HDFS-7240.003.patch,
> HDFS-12235-HDFS-7240.004.patch, HDFS-12235-HDFS-7240.005.patch,
> HDFS-12235-HDFS-7240.006.patch, HDFS-12235-HDFS-7240.007.patch
>
>
> KSM and SCM interaction for delete key operation, both KSM and SCM stores key
> state info in a backlog, KSM needs to scan this log and send block-deletion
> command to SCM, once SCM is fully aware of the message, KSM removes the key
> completely from namespace. See more from the design doc under HDFS-11922,
> this is task break down 2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
