flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhaoshijie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-11139) stream non window join support state ttl
Date Thu, 13 Dec 2018 15:52:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-11139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720330#comment-16720330

zhaoshijie commented on FLINK-11139:

[~hequn8128] ok. we use stream non window join(this part of code we use Flink 1.6.0 ) in
actual production ,taskManger will OOM when there is a long expiration time。so ,we try
to clean expired data by state ttl,so I think is a way to deal with too many timer on Heap.

[~fhueske] if use ttl , i think we dont need minRetentionTime and maxRetentionTime ,we just
need config state update strategy.

> stream non window join support state ttl
> ----------------------------------------
>                 Key: FLINK-11139
>                 URL: https://issues.apache.org/jira/browse/FLINK-11139
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>    Affects Versions: 1.7.0
>            Reporter: zhaoshijie
>            Priority: Major
> stream non window join function use timer to delete expired data,it is ok for small
amount of data or short expiration time,but it will be OOM(too many timer)on taskManger
 when there  is a long expiration time and  a large amount of data。In fact, table module
other state function has same problem,I would like to contribute to fix it。

This message was sent by Atlassian JIRA

View raw message