Hi everyone, I've updated the "Future Work" section to include a proposed mechanism for tracking whether dynamic configurations have been successfully applied across all servers. I've also added an explanation of why not implement it in this FIP now.
Thank you all for your valuable feedback. If there are no further concerns, I plan to start the vote shortly. Best regards, Hongshun On Thu, Aug 7, 2025 at 11:51 AM Hongshun Wang <[email protected]> wrote: > Hi devs, > > I'd like to start a discussion about FIP-12: Server Dynamic Config[1]. > Currently, any changes to the server.yaml configuration in a Fluss cluster > require a full restart of the cluster, which negatively impacts stability > and availability. To improve operational agility and reduce downtime, we > propose introducing dynamic configuration capabilities, enabling runtime > modification of key parameters—such as enabling/disabling lake-streaming > integration features or managing user accounts—without requiring service > interruption. > > The POC[2] code is provided to enable lake format. You can try and give > some advice. > > Best > Hongshun > > > [1] > https://cwiki.apache.org/confluence/display/FLUSS/FIP-12%3A+Server+Dynamic+Config > [2] https://github.com/loserwang1024/fluss/tree/poc-dymanic-config. >
