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/03/16 13:15:00 UTC

[jira] [Updated] (FLINK-26685) Investigate/improve tests stability when using InMemory Changelog implementation

     [ https://issues.apache.org/jira/browse/FLINK-26685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Khachatryan updated FLINK-26685:
--------------------------------------
        Parent: FLINK-25842
    Issue Type: Sub-task  (was: Improvement)

> Investigate/improve tests stability when using InMemory Changelog implementation
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-26685
>                 URL: https://issues.apache.org/jira/browse/FLINK-26685
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / State Backends, Test Infrastructure
>    Affects Versions: 1.15.0, 1.16.0
>            Reporter: Roman Khachatryan
>            Priority: Major
>             Fix For: 1.16.0
>
>
> Large scale tests often fail when using InMemory Changelog, either because of excessive GC pressure, serialization, or exceeding memory limits.
> So far, it was fixed by using FS implementation on a case-by-case basis. Always using FS isn't straightforward.
> Investigate if there are any ways to uniformly use FS impl. or stabilize in-memory impl.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)