Hi! I see that SPARK-1537 is now closed as won't fix. What was the
reason the Spark community decided to skip ATSv2 support?
My org is currently looking at how we introduce Spark into YARN clusters
that are primarily used for Scalding today. For the Scalding UI we use
an internal tool
This seem like not very impactful for end-users on K8s assuming they've got
logging of some kind set up. Unless I'm missing something.
On Tue, Apr 21, 2020 at 4:51 PM edeesis wrote:
> I'd like to advocate for:
>
> https://issues.apache.org/jira/browse/SPARK-25515
> and
>
I'd like to advocate for:
https://issues.apache.org/jira/browse/SPARK-25515
and
https://issues.apache.org/jira/browse/SPARK-29865
Two small QOL changes that make production use of Spark with Kubernetes much
easier.
--
Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/
I have one: https://issues.apache.org/jira/browse/SPARK-31485, which could
cause application hang.
And, probably, also https://issues.apache.org/jira/browse/SPARK-31509, to
make better guidance of barrier execution for user. But we do not have
conclusion yet.
Best,
Yi Wu
--
Sent from:
