yaooqinn opened a new pull request, #52886: URL: https://github.com/apache/spark/pull/52886
### What changes were proposed in this pull request? Deprecated spark.shuffle.server.chunkFetchHandlerThreadsPercent first, and then we can remove chunkFetchHandler usages in the future. ### Why are the changes needed? In the Netty project, those related APIs are - removed from the main branch https://github.com/netty/netty/pull/8778 - and deprecated in 4.2 branch https://github.com/netty/netty/pull/14538 ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? <!-- If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible. If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future. If tests were not added, please describe why they were not added and/or why it was difficult to add. If benchmark tests were added, please run the benchmarks in GitHub Actions for the consistent environment, and the instructions could accord to: https://spark.apache.org/developer-tools.html#github-workflow-benchmarks. --> I verified this by a SparkPi local test ```scala bin/run-example -c spark.shuffle.server.chunkFetchHandlerThreadsPercent=10 SparkPi WARNING: Using incubator modules: jdk.incubator.vector Using Spark's default log4j profile: org/apache/spark/log4j2-defaults.properties 25/11/05 10:59:14 WARN SparkConf: The configuration key 'spark.shuffle.server.chunkFetchHandlerThreadsPercent' has been deprecated as of Spark 4.2.0 and may be removed in the future. Using separate chunkFetchHandlers could be problematic due to the underlying netty layer ``` ### Was this patch authored or co-authored using generative AI tooling? no -- 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]
