runzhiwang commented on pull request #1504: URL: https://github.com/apache/ozone/pull/1504#issuecomment-729393625
> How about supporting truncate only at block level granularity i.e, If a key needs to be truncated, change the lengths of the partial block to be truncated in OM and all the other blocks which need to be deleted fully can just be deleted . These blocks can then by picked by KeyDeleting service in OM and will get deleted by Delete Workflow in ozone? @bshashikant +1, thanks the suggestion. With this suggestion, for the partially truncate block, we only need to change the block length in OM, and do not need to change SCM and Datanode. the work become easy. The only cons is we waste maxum 128MB (size of block) of disk of each truncate operation, because we do not process the partially truncate block. But because truncate happen sparsely, so it's not a problem. If we want to process the partially truncate block to save disk capacity, we can still do it in future, it's compatible with current design. @GlenGeng @xiaoyuyao What do you think ? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
