[
https://issues.apache.org/jira/browse/FLINK-35746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004944#comment-18004944
]
Nishita Pattanayak commented on FLINK-35746:
--------------------------------------------
[~gyfora] I can take a look at this.
Here is a suggested implementation do let me know if I can take it up.
*Current Implementation:*
FlinkConfigManager -> ObserveConfig -> Operator decides based on observerConfig
*New Implementation:*
FlinkConfigManager -> ObserveConfig -> REST API Query → Actual Config from
application and Observer Config -> Final ObserveConfig -> Operator decides
based on final config
We have to implement method: `getEffectiveConfiguration` to get the
configuration from JMs and application via the restClient. This would help us
get the actual configuration being run and ensure there is no discrepancy
between operator and application.
> Add logic to override observed config based on settings observed through REST
> API
> ---------------------------------------------------------------------------------
>
> Key: FLINK-35746
> URL: https://issues.apache.org/jira/browse/FLINK-35746
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Major
>
> In many cases the Flink operator relies on the user configuration to infer
> running application/cluster settings. While this is mostly fine, many of
> these configs can be programmatically changed by the user in their app main
> method that will ultimately take precedence and can lead to inconsistent
> behaviour from the operators side.
> To alleviate this we need to add logic to override parts of the observed
> config based on what we see from the cluster. Such as checkpointing enabled /
> disabled, checkpoint intervals etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
