swuferhong opened a new issue, #3613: URL: https://github.com/apache/fluss/issues/3613
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Motivation Fluss currently relies mainly on `max.bucket.num` and `max.partition.num` to limit table metadata size. These limits do not directly protect the cluster from creating too many KV leader replicas, which can consume resident memory on `TabletServers` and increase OOM risk. We need a coordinator-side capacity guard that can estimate the total KV leader replica capacity from TabletServer memory and reject new KV table/partition creation when the cluster no longer has enough capacity. ### Solution _No response_ ### Anything else? _No response_ ### Willingness to contribute - [ ] I'm willing to submit a PR! -- 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]
