Thanks Hongshun for updating the FIP, the updated doc looks good to me. It’s a good time to start vote if no more feedbacks.
One minor suggestion that Future Work section will help users understand your design and tradeoff better. Best, Leonard > 2025 8月 13 14:19，Wang Cheng <[email protected]> 写道： > > Noted. Thanks for your reply. > > > > Regards, > Cheng > > > > > > > > > ------------------ Original ------------------ > From: > "dev" > > <[email protected] <mailto:[email protected]>>; > Date: Wed, Aug 13, 2025 01:59 PM > To: "dev"<[email protected] <mailto:[email protected]>>; > > Subject: Re: [DISCUSS] FIP-12: Server Dynamic Config > > > > Hi Cheng, > > Since tablet servers lazily apply config changes, could we provide an RPC > call like IsAlterConfigDone to allow users to track the progress? > > I've discussed with Jark again, and we agree that this should be > implemented in its final form, but not right now. I'll add it to the > "Future Work" section of this FIP. > > Best > Hongshun > > On Fri, Aug 8, 2025 at 10:39 AM Wang Cheng <[email protected]> > wrote: > > > Hi Hongshun, > > > > > > > > Since tablet servers lazily apply config changes, could we provide an RPC > > call like IsAlterConfigDone to allow users to track the progress? > > > > 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 for > > dynamic server-level and table-level configurations. In modern > distributed > > databases like PGXL [1] (a distributed PostgreSQL variant), both DDL > > operations and SET commands are handled uniformly via a two-phase > commit > > protocol 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 > > > > > > > > &nbsp; > > > > > > > > > > ------------------ Original ------------------ > > From: > > > "dev" > > > < > > [email protected] <mailto:[email protected]>&gt;; > > Date:&nbsp;Thu, Aug 7, 2025 11:51 AM > > To:&nbsp;"dev"<[email protected] > <mailto:[email protected]>&gt;; > > > > Subject:&nbsp;[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.
