smengcl commented on code in PR #11451: URL: https://github.com/apache/ozone/pull/11451#discussion_r4225724633
########## THREAT_MODEL.md: ########## @@ -328,6 +337,7 @@ Per-boundary input trust (grouped by family): ideally, encrypt them on disk. *(maintainer โ jojochuang, 2026-06-25.)* - **Isolate the KMS** in a separate, firewalled network segment. *(maintainer โ jojochuang, 2026-06-25.)* +- **Bound client load:** set namespace and space quotas, enable the RPC `FairCallQueue` on the OM (for S3 traffic it needs the Ozone identity provider), and put rate limiting in front of an internet-facing S3 Gateway. Ozone does not promise to withstand load by volume (ยง9). Review Comment: Added in 3eeb3c33c75: the guidance now says FairCallQueue covers S3 traffic only when S3 Gateway reaches the OM over Hadoop RPC, not over gRPC. One correction to the comment: Hadoop RPC is the default (`ozone.om.transport.class` defaults to `Hadoop3OmTransportFactory`). `ozone.om.s3.grpc.server_enabled=true` only opens the OM gRPC endpoint, S3 Gateway uses it only when the transport class is set to `GrpcOmTransportFactory`. So no switch is required on a default setup. _๐ค Addressed by [Claude Code](https://claude.com/claude-code)_ -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
