dongjoon-hyun commented on PR #39825: URL: https://github.com/apache/spark/pull/39825#issuecomment-1421976910
Yes, last week, I was only -1 for [SPARK-42261 K8s will not allocate more execs if there are any pending execs until next snapshot](https://issues.apache.org/jira/browse/SPARK-42261) part because it's reported as a bug. For SPARK-42260, I wasn't sure because its `Target Version` was `3.4.1`. For the following, I'm open for new feature approaches. > What about if we use "allocation batch size" to gate it like @attilapiros suggested? For the following (which is more important), I didn't catch up on this PR's latest commits yet, but I didn't mean to prevent alternatives. Even in Spark 3.4, I believe we can backport a required K8s alternatives still if we need it, @holdenk . > But more to the point: does having this as an opt-in feature make you feel comfortable with dropping the -1? Or do you think that having this an optional feature is bad? I think it's reasonable for us to want to support non-EKS deployments for fast scale up (not everyone is going to use EKS let alone PVCs on EKS). -- 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]
