Re: [DISCUSS] FIP-12: Server Dynamic Config

[Wang Cheng]

Noted. Thanks for your reply.



Regards,
Cheng



 




------------------ Original ------------------
From:                                                                           
                                             "dev"                              
                                                      
<loserwang1...@gmail.com&gt;;
Date:&nbsp;Wed, Aug 13, 2025 01:59 PM
To:&nbsp;"dev"<dev@fluss.apache.org&gt;;

Subject:&nbsp;Re: [DISCUSS] FIP-12: Server Dynamic Config



Hi Cheng,
&gt; 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?6?2AM Wang Cheng <348448...@qq.com.invalid&gt; 
wrote:

&gt; Hi Hongshun,
&gt;
&gt;
&gt;
&gt; Since tablet servers lazily apply config changes, could we provide an RPC
&gt; call like IsAlterConfigDone to allow users ?6?7?6?7to track the 
progress?6?7?6?7?
&gt;
&gt; Do we have a RESET command to restore the value of a run-time parameter to
&gt; the default value?
&gt;
&gt; I'm still unclear about the need for two distinct implementations?6?7?6?7 
for
&gt; dynamic server-level and table-level configurations. In modern distributed
&gt; databases like ?6?7?6?7PGXL [1] (a distributed PostgreSQL 
variant)?6?7?6?7, both DDL
&gt; operations and SET commands ?6?7?6?7are handled uniformly via a two-phase 
commit
&gt; protocol?6?7?6?7 to avoid any inconsistency problems across all data nodes 
and
&gt; coordinators.
&gt;
&gt;
&gt;
&gt; [1]
&gt; 
https://postgres-x2.github.io/presentation_docs/2014-07-PGXC-Implementation/pgxc.pdf
&gt;
&gt;
&gt;
&gt; Regards,
&gt; Cheng
&gt;
&gt;
&gt;
&gt; &amp;nbsp;
&gt;
&gt;
&gt;
&gt;
&gt; ------------------ Original ------------------
&gt; From:
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 "dev"
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 <
&gt; loserwang1...@gmail.com&amp;gt;;
&gt; Date:&amp;nbsp;Thu, Aug 7, 2025 11:51 AM
&gt; To:&amp;nbsp;"dev"<dev@fluss.apache.org&amp;gt;;
&gt;
&gt; Subject:&amp;nbsp;[DISCUSS] FIP-12: Server Dynamic Config
&gt;
&gt;
&gt;
&gt; Hi devs,
&gt;
&gt; I'd like to start a discussion about FIP-12: Server Dynamic Config[1].
&gt; Currently, any changes to the server.yaml configuration in a Fluss cluster
&gt; require a full restart of the cluster, which negatively impacts stability
&gt; and availability. To improve operational agility and reduce downtime, we
&gt; propose introducing dynamic configuration capabilities, enabling runtime
&gt; modification of key parameters??such as enabling/disabling lake-streaming
&gt; integration features or managing user accounts??without requiring service
&gt; interruption.
&gt;
&gt; The POC[2] code is provided to enable lake format. You can try and give
&gt; some advice.
&gt;
&gt; Best
&gt; Hongshun
&gt;
&gt;
&gt; [1]
&gt;
&gt; 
https://cwiki.apache.org/confluence/display/FLUSS/FIP-12%3A+Server+Dynamic+Config
&gt; [2] https://github.com/loserwang1024/fluss/tree/poc-dymanic-config.