[
https://issues.apache.org/jira/browse/FLINK-34001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804092#comment-17804092
]
yong yang commented on FLINK-34001:
-----------------------------------
left table is(tb1) 1000000/s input. and large id not exists in tb2;
my lookup.cache config is 1000000,but tb2(mysql) ,flink backpressure is often
caused by excessive load;
Does lookup.cache have an upper limit? Does a configuration of hundreds of
millions cause poor cache performance?
> Fix ambiguous document description towards the default value for configuring
> operator-level state TTL
> -----------------------------------------------------------------------------------------------------
>
> Key: FLINK-34001
> URL: https://issues.apache.org/jira/browse/FLINK-34001
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, Table SQL / API
> Affects Versions: 1.18.0
> Reporter: yong yang
> Assignee: Jane Chan
> Priority: Major
> Labels: pull-request-available
>
> doc:
> https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/dev/table/concepts/overview/#idle-state-retention-time
> The current TTL value for both left and right side is {{{}"0 ms"{}}}, which
> means the state retention is not enabled.
>
> but i test find :
> The current TTL value for both left and right side is {{{}"0 ms"{}}}, which
> means the state is permanence keep!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
