You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Roman Khachatryan (Jira)" <ji...@apache.org> on 2022/08/26 12:00:00 UTC
[jira] [Closed] (FLINK-28976) Changelog 1st materialization delayed unneccesarily
[ https://issues.apache.org/jira/browse/FLINK-28976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Khachatryan closed FLINK-28976.
-------------------------------------
Resolution: Fixed
Merged into master as 91e1291e942afc69779f09ead549352d5d357f22 .. a38b852bbbdb812aa404c226717a2fa3bdd89665,
into release-1.15 as 493a1aa8556038283e256efc5368bd319bd06d17 .. 258c3e35265bb3a966bd317340f2a5fe7cfd7364.
> Changelog 1st materialization delayed unneccesarily
> ---------------------------------------------------
>
> Key: FLINK-28976
> URL: https://issues.apache.org/jira/browse/FLINK-28976
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
> Affects Versions: 1.15.1, 1.16.0
> Reporter: Roman Khachatryan
> Assignee: Roman Khachatryan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0, 1.15.3
>
>
> In PeriodicMaterializationManager.start(), the 1st materialization is scheduled with a delay: materialization_interval + random_offset
> Here, random_offset is added to avoid thundering herd problem.
> The next materialization will be scheduled with a delay of only materialization_interval.
> That means that the 1st materialization will have to compact up to 2 times more state changes than the subsequent ones.
> Which in turn can cause FLINK--26590 or other problems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)