Copilot commented on code in PR #11451: URL: https://github.com/apache/ozone/pull/11451#discussion_r4225492426
########## 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: The FairCallQueue recommendation omits that the default S3 Gateway-to-OM transport is gRPC (`ozone.om.s3.grpc.server_enabled=true`), while FairCallQueue has no gRPC implementation. Configuring only the identity provider therefore leaves default S3 traffic unprotected; explicitly require switching S3 Gateway to Hadoop RPC before enabling FairCallQueue (see `hadoop-hdds/docs/content/feature/FairCallQueue.md:21-28,44-63` and `hadoop-hdds/common/src/main/resources/ozone-default.xml:4502-4508`). -- 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]
