You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2022/07/19 06:49:00 UTC
[jira] [Closed] (FLINK-28582) LSM tree structure may be incorrect when multiple jobs are committing into the same bucket
[ https://issues.apache.org/jira/browse/FLINK-28582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jingsong Lee closed FLINK-28582.
--------------------------------
Resolution: Fixed
master: f34be4ba159341d52eced8f7d0b0a5afc97ff91f
> LSM tree structure may be incorrect when multiple jobs are committing into the same bucket
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-28582
> URL: https://issues.apache.org/jira/browse/FLINK-28582
> Project: Flink
> Issue Type: Bug
> Components: Table Store
> Affects Versions: table-store-0.2.0
> Reporter: Caizhi Weng
> Assignee: Caizhi Weng
> Priority: Blocker
> Labels: pull-request-available
> Fix For: table-store-0.2.0
>
>
> Currently `FileStoreCommitImpl` only checks for conflicts by checking the files we're going to delete (due to compaction) are still there.
> However, consider two jobs committing into the same LSM tree at the same time. For their first compaction no conflict is detected because they'll only delete their own level 0 files. But they will both produce level 1 files and the key ranges of these files may overlap. This is not correct for our LSM tree structure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)