ivoson commented on PR #55891: URL: https://github.com/apache/spark/pull/55891#issuecomment-4485221347
> The commit body already documents this correctly: pre-rollout hardening for the bounded merge factor (default disabled); reachable on deployments that enable the feature and run a SparkPlugin whose MemoryConsumer spills from non-task threads (Comet/Gluten/RAPIDS/Photon are listed as instances); `SparkPlugin` / `TaskContext.taskMemoryManager` are public API, and non-task-thread `MemoryConsumer.spill()` is a real production path with [SPARK-39283](https://issues.apache.org/jira/browse/SPARK-39283) (task vs sibling-consumer spill deadlock fix) as precedent. The GitHub PR description still says "defensive protection / not triggered in existing code", which contradicts that. Suggest rewriting the PR description to mirror the commit body. JIRA Affected Versions and any backport to `branch-4.2` are for the author and shepherding committer to decide. updated PR description. -- 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]
