You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (Jira)" <ji...@apache.org> on 2023/11/16 10:22:00 UTC
[jira] [Closed] (FLINK-33572) Minimize ConfigMap API operations for autoscaler state
[ https://issues.apache.org/jira/browse/FLINK-33572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maximilian Michels closed FLINK-33572.
--------------------------------------
Release Note: Implemented via 02840b96ef3116ea95a440af4f945398900d89df and ab0ec081eac86619a22632616fa4c01c074ecd33.
Resolution: Fixed
> Minimize ConfigMap API operations for autoscaler state
> ------------------------------------------------------
>
> Key: FLINK-33572
> URL: https://issues.apache.org/jira/browse/FLINK-33572
> Project: Flink
> Issue Type: Improvement
> Components: Autoscaler, Kubernetes Operator
> Affects Versions: kubernetes-operator-1.6.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.7.0
>
>
> The newly introduced flush operation after the refactoring the autoscaler interfaces, optimizes the number of write operations to the underlying state store. A couple of further optimizations:
> 1. Any writes should be deferred until flush is called.
> 2. The flush routine should detect whether a write is needed and writing if there are no changes
> 3. Clearing state should only require one write operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)