> As more people joined the development of Pulsar and more PIPs are > opened, I found the configurations became very large. At the moment > for commit 9917aac, there are 426 configuration items in broker.conf, > which is too many. I agree with you, the configuration of pulsar is too complicated, we should optimize its usage
> > I have an idea that we can split `ServiceConfiguration` into different > configuration classes. We need to ensure version compatibility, so we have to write a lot of unnecessary code and this also means we need multiple configuration files, which seems to only optimize the user experience a little. How about creating a script like pulsar-admin, of course, it only deals with broker configuration changes and searches, etc. We classify the configuration items of broker.conf, and users can search according to specific categories. like managed ledger, offload, transaction, schema etc. ``` ./pulsar-conf broker lookup ./pulsar-conf broker modify ``` Thanks, Bo
