merlimat commented on PR #26008: URL: https://github.com/apache/pulsar/pull/26008#issuecomment-4693657856
> LGTM. Just one remaining question: when a user changes the overrides for a namespace or topic, is there some way to trigger autoscaling immediately? Let's say that the user increases the `minSegments` or `maxSegments` where the current number of segments is out of the bounds. I would assume that such an operation would be preferred over the current manual autosplit/merge operations available in the Admin REST API for scalable topics. Right now, it would be check at next interval. Though it could be good have a way to immediately correct. I'd leave it out of the scope of this PR though, since the behavior on a namespace config change should also be considered. > Related to `minSegments`, is it already possible to create a topic with a given amount of `minSegments` initially, or does it always start from 1? Perhaps there would need to be a separate `initialSegments` in that case since `minSegments` seems to be meant for the minimum number of segments where further merges would no longer take place. It's already possible to specify the number of segments on the topic creation. Eventually that would be adjusted by auto split/merge -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
