jojochuang opened a new pull request, #10792: URL: https://github.com/apache/ozone/pull/10792
## What changes were proposed in this pull request? Rooted OFS `getFileStatus()` on normal bucket/key paths (non-snapshot) previously called `getBucket()` → InfoBucket, then `bucket.getFileStatus()`, which is already `proxy.getOzoneFileStatus()`. This PR skips the redundant **InfoBucket** RPC and calls **`GetFileStatus` only** via `proxy.getOzoneFileStatus(..., headOp)`. Snapshot indicator paths are unchanged: they still use `getBucket()` and synthetic status (no `GetFileStatus`). **Behavior change (accepted):** Client-side `validateBucketLayout()` no longer runs on the stat path. OM accepts `GetFileStatus` for **OBJECT_STORE** buckets, so rooted `getFileStatus` may succeed or return `FILE_NOT_FOUND` instead of throwing `IllegalArgumentException`. Mutating OFS operations (`mkdir`, `create`, `delete`, etc.) still call `getBucket()` and reject OBJECT_STORE as before. This is a **client-side** optimization for [HDDS-15925](https://issues.apache.org/jira/browse/HDDS-15925). It is **not** the [HDDS-11232](https://issues.apache.org/jira/browse/HDDS-11232) approach (no combined OM response / server-side merge of bucket info with file status). HDDS-15925 references HDDS-11232 for the same RPC-reduction theme. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-15925 ## How was this patch tested? - [x] Unit: `TestBasicRootedOzoneClientAdapterHeadOp` (direct `getOzoneFileStatus` / `headOp`) - [x] Integration: `TestOFS#testGetFileStatusUsesSingleOmRpc` (OM metrics: no InfoBucket increment, `GetFileStatus` +1 per stat) - [x] Integration: missing-bucket stat expects `FileNotFoundException` (client mapping) - [x] Smoketest: `ozonefs-obs.robot` updated for OBS stat vs mutating ops - [x] CI on https://github.com/apache/ozone/pull/10792 Generated-by: Cursor (Composer) -- 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]
