Thanks Hangxiang Yu, Please find the answers below
1. Yes, we should perform validation before trying to update the configuration. I'd rather validate some specific options that are known to not work though. Finding and hard-coding all the valid options might be impractical since they can change, and non trivial. 2. That would be great, but we'd have to store the history of such updates somewhere. For debugging purposes, logs should suffice I think 3. That's a great question! Configuration changes are applied immediately; resource requirements changes are applied with some delay; and both are stored in HA immediately. So configuration change request results also in restarting and applying why pending resource requirements changes Regards, Roman On Fri, May 9, 2025, 05:10 Hangxiang Yu <master...@gmail.com> wrote: > Hi, Roman. > > Thanks for the FLIP. > +1 for supporting dynamic configuration to reduce manual restart. > > > I just have below questions: > > 1. Do we need a working configuration list ? So some unsupported > configurations could be rejected in advance. > > 2. Could we show the change history in the Web UI ? So more changed details > could be tracked. > > 3. How does it co-works with other dynamic requests ? For example, it > modifies the parallelisms together with ' > /jobs/:jobid/resource-requirements'. > > On Fri, May 9, 2025 at 5:00 AM Roman Khachatryan <ro...@apache.org> wrote: > > > Hi everyone, > > > > I would like to start a discussion about FLIP-530: Dynamic job > > configuration [1]. > > > > In some cases, it is desirable to change Flink job configuration after it > > was submitted to Flink, for example: > > - Troubleshooting (e.g. increase checkpoint timeout or failure threshold) > > - Performance optimization, (e.g. tuning state backend parameters) > > - Enabling new features after testing them in a non-Production > environment. > > This allows to de-couple upgrading to newer Flink versions from actually > > enabling the features. > > To support such use-cases, we propose to enhance Flink job configuration > > REST-endpoint with the support to read full job configuration; and update > > it. > > > > Looking forward to feedback. > > > > [1] > > https://cwiki.apache.org/confluence/x/uglKFQ > > > > Regards, > > Roman > > > > > -- > Best, > Hangxiang. >
