[ https://issues.apache.org/jira/browse/FLINK-32810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fan Hong updated FLINK-32810: ----------------------------- Description: Right now, by default, an instance of `ListStateWithCache` uses up all the managed memory allocated for`ManagedMemoryUseCase.OPERATOR`. It could bring some bugs in some situations, for example, when there exist more than one `ListStateWithCache`s in a single operator, or there are other places using managed memory of `ManagedMemoryUseCase.OPERATOR`. An approach to resolve such cases is to let the developer be aware about the usage of managed memory of `ManagedMemoryUseCase.OPERATOR`, instead of implicitly use up all of it. Therefore, I think it is better to add a parameters `fraction` to specify how much memory is used in the `ListStateWithCache`. was: Right now, by default, `ListStateWithCache` will use up all the managed memory allocated for`ManagedMemoryUseCase.OPERATOR`. It could bring some bugs in some situations. For example, there exist more than one `ListStateWithCache`s in a single operator, or there are other places using managed memory of `ManagedMemoryUseCase.OPERATOR`. An approach to resolve such cases is to let the developer of the operator be aware about the usage of managed memory of `ManagedMemoryUseCase.OPERATOR`, instead of implicitly use up all of it. Therefore, I think it is better to add a parameters `fraction` to specify how much memory is used in the `ListStateWithCache`. > Improve managed memory usage in ListStateWithCache > -------------------------------------------------- > > Key: FLINK-32810 > URL: https://issues.apache.org/jira/browse/FLINK-32810 > Project: Flink > Issue Type: Improvement > Components: Library / Machine Learning > Reporter: Fan Hong > Priority: Major > > Right now, by default, an instance of `ListStateWithCache` uses up all the > managed memory allocated for`ManagedMemoryUseCase.OPERATOR`. > It could bring some bugs in some situations, for example, when there exist > more than one `ListStateWithCache`s in a single operator, or there are other > places using managed memory of `ManagedMemoryUseCase.OPERATOR`. > > An approach to resolve such cases is to let the developer be aware about the > usage of managed memory of `ManagedMemoryUseCase.OPERATOR`, instead of > implicitly use up all of it. Therefore, I think it is better to add a > parameters `fraction` to specify how much memory is used in the > `ListStateWithCache`. -- This message was sent by Atlassian Jira (v8.20.10#820010)