My thoughts are, External shuffle service is not a blocker for spark on k8s
to be a production ready.
Others may think otherwise, but there are other ways to enable auto
scaling. External shuffle service feature will be useful for all the ways
of deployments be it yarn, standalone, k8s and not jus
Sounds good. I think we can make a slightly stronger statement than that
one (left a comment, but it's my own thoughts so others should chime in if
they have a different opinion).
On Wed, Aug 5, 2020 at 7:32 PM Takeshi Yamamuro
wrote:
> Thanks for the info, all. okay, I understood that we need m
Thanks for the info, all. okay, I understood that we need more time to
announce GA officially.
But, I'm still worried that users hesitate a bit to use this feature by
referring to the statement in the doc,
so how about updating it according to the current situation? Please check
my suggestion in ht
Thank you so much Rohit!
2020년 8월 5일 (수) 오후 4:59, Rohit Mishra 님이 작성:
> Thanks, Hyukjin. I will go through the reference links you have provided
> and will reach out to understand what is the best place to start. Thanks
> for adding tips for new contributors like me.
>
> Regards,
> Rohit Mishra
>
Mostly echoing stuff that we've discussed in
https://github.com/apache/spark/pull/29180, but good to have this also on
the dev-list.
> So IMO maintaining outside in a separate repo is going to be harder. That
was why I asked.
I agree with Felix, having this inside of the project would make it muc
Thanks, Hyukjin. I will go through the reference links you have provided
and will reach out to understand what is the best place to start. Thanks
for adding tips for new contributors like me.
Regards,
Rohit Mishra
On Wed, Aug 5, 2020 at 12:12 PM Hyukjin Kwon wrote:
> Hi all,
>
> I am trying to
