You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Yingchun Lai (Jira)" <ji...@apache.org> on 2022/11/14 02:39:00 UTC
[jira] [Commented] (KUDU-3367) Delta file with full of delete op can not be schedule to compact
[ https://issues.apache.org/jira/browse/KUDU-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633458#comment-17633458 ]
Yingchun Lai commented on KUDU-3367:
------------------------------------
[~zhangyifan27] KUDU-1625 depends the tablet supports 'live row count' (which is introduced since Kudu 1.12 ?), even if upgrading Kudu to a higher version, the old exists tablet still doesn't have such metadata, so the DeletedRowsetGCOp will not work on these tablets.
I guess [~Koppa] is trying to make these old tablet is able to GC such rowsets whose rows full deleted, right?
> Delta file with full of delete op can not be schedule to compact
> ----------------------------------------------------------------
>
> Key: KUDU-3367
> URL: https://issues.apache.org/jira/browse/KUDU-3367
> Project: Kudu
> Issue Type: New Feature
> Components: compaction
> Reporter: dengke
> Assignee: dengke
> Priority: Major
> Attachments: image-2022-05-09-14-13-16-525.png, image-2022-05-09-14-16-31-828.png, image-2022-05-09-14-18-05-647.png, image-2022-05-09-14-19-56-933.png, image-2022-05-09-14-21-47-374.png, image-2022-05-09-14-23-43-973.png, image-2022-05-09-14-26-45-313.png, image-2022-05-09-14-32-51-573.png
>
>
> If we get a REDO delta with full of delete op, wich means there is no update op in the file. The current compact algorithm will not schedule the file do compact. If such files exist, after accumulating for a period of time, it will greatly affect our scan speed. However, processing such files every time compact reduces compact's performance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)