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.

Reply via email to