Hi Hongshun,
Since tablet servers lazily apply config changes, could we provide an RPC call like IsAlterConfigDone to allow users ?6?7?6?7to track the progress?6?7?6?7? Do we have a RESET command to restore the value of a run-time parameter to the default value? I'm still unclear about the need for two distinct implementations?6?7?6?7 for dynamic server-level and table-level configurations. In modern distributed databases like ?6?7?6?7PGXL [1] (a distributed PostgreSQL variant)?6?7?6?7, both DDL operations and SET commands ?6?7?6?7are handled uniformly via a two-phase commit protocol?6?7?6?7 to avoid any inconsistency problems across all data nodes and coordinators. [1] https://postgres-x2.github.io/presentation_docs/2014-07-PGXC-Implementation/pgxc.pdf Regards, Cheng ------------------ Original ------------------ From: "dev" <[email protected]>; Date: Thu, Aug 7, 2025 11:51 AM To: "dev"<[email protected]>; Subject: [DISCUSS] FIP-12: Server Dynamic Config 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.
