flink-issues mailing list archives

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

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

Hequn Cheng commented on FLINK-11139:
-------------------------------------

[~fhueske] Thanks for the reminder. Yes it will add 8 bytes per stored value. I think we should
do a trade-off between OOM and the performance regression.


 [~zhaoshijie] Do you have some performance tests? Would be great if you can provide some
information about the influences on performance.

Best, Hequn

> 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
>            Assignee: 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
(v7.6.3#76005)

Mime
View raw message