shunping opened a new issue, #39548: URL: https://github.com/apache/beam/issues/39548
### What happened? ## Description It has been reported that some pipelines are running slower after upgrading Beam SDK to 2.74+. Particularly, users observed increased CPU, memory usage, and wall time for those jobs. ## Root Cause We suspect the culprit is gcs-connector, since we bumped its version from 2.x to 3.x in release 2.74. Specifically, in gcs-connector v3, `GoogleCloudStorageReadOptions.DEFAULT` changed its default fadvise behavior from `SEQUENTIAL` to `AUTO`. This change disrupts expected sequential read throughput and caching behavior, which leads to the observed performance degradation or even stuck jobs. ## References A separate investigation documented in the upstream Hadoop connectors repository has confirmed this behavior: [GoogleCloudDataproc/hadoop-connectors#1762](https://github.com/GoogleCloudDataproc/hadoop-connectors/pull/1762) Internal bugs: 535192796, 512366613, 535194786. ### Issue Priority Priority: 2 (default / most bugs should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [x] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Prism Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- 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]
