You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2017/05/02 21:14:04 UTC
[jira] [Commented] (KUDU-1089) schedule delayed fsync of metadata
blocks after block deletion
[ https://issues.apache.org/jira/browse/KUDU-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993763#comment-15993763 ]
Adar Dembo commented on KUDU-1089:
----------------------------------
[~mpercy] can you comment further on this bug? What do you mean by 'orphaned blocks'?
If these are blocks that the block manager knows about but don't belong to any tablets, I don't see how a delayed fsync of deletion metadata helps.
If these are missing hole punches, I think I've addressed that in KUDU-1857.
> schedule delayed fsync of metadata blocks after block deletion
> --------------------------------------------------------------
>
> Key: KUDU-1089
> URL: https://issues.apache.org/jira/browse/KUDU-1089
> Project: Kudu
> Issue Type: Bug
> Components: fs
> Affects Versions: Public beta
> Reporter: Mike Percy
>
> We should do a delayed fsync of metadata block after block deletion so we don't leave orphaned blocks on the filesystem.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)