[
https://issues.apache.org/jira/browse/HDDS-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937349#comment-16937349
]
Dinesh Chitlangia edited comment on HDDS-2017 at 9/25/19 3:28 AM:
------------------------------------------------------------------
After comments from [~arp] and discussions with [~aengineer], we decided not to
implement this check command and instead we simply delete the encryption key
details from key metadata before we move it to deletedTable. This new change
will be done in HDDS-2174
was (Author: dineshchitlangia):
After comments from [~arp] and discussions with [~aengineer], we decided not to
implement this check command and instead we simply delete the encryption key
details from key metadata before we move it to deletedTable.
> Add option to confirm if a key has been deleted from DeletedKeys table in OM
> ----------------------------------------------------------------------------
>
> Key: HDDS-2017
> URL: https://issues.apache.org/jira/browse/HDDS-2017
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Dinesh Chitlangia
> Assignee: Dinesh Chitlangia
> Priority: Major
> Attachments: HDDS-2017.draft.patch
>
>
> When a client requests for a key to be deleted, OM moves the corresponding
> KeyInfo to DELETED_TABLE in OM Metadata.
> As part of GDPR implementation, once the KeyInfo is also deleted from this
> DELETED_TABLE tablespace, the admin can officially confirm that the key has
> been deleted from the system since the metadata is lost and there is no way
> to decrypt the blocks.
> This jira aims to add an option to check if a key has been deleted from
> DELETED_TABLE tablespace or not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
