Hi,
The minimal solution is to enable dynamicAllocation and set idle timeout to
low value. This will ensure that idle executors are killed and resources
available for others to use,
spark.dynamicAllocation.enabled
spark.dynamicAllocation.executorIdleTimeout
If you would like to understand
Yes. At this rate I think it's better to do 2.4 next, followed by 3.0.
On Fri, Jun 15, 2018 at 10:52 AM Mridul Muralidharan
wrote:
> I agree, I dont see pressing need for major version bump as well.
>
>
> Regards,
> Mridul
> On Fri, Jun 15, 2018 at 10:25 AM Mark Hamstra
> wrote:
> >
> >
+1
On Fri, Jun 15, 2018 at 7:10 AM, Tom Graves
wrote:
> +1 for doing a 2.1.3 release.
>
> Tom
>
> On Wednesday, June 13, 2018, 7:28:26 AM CDT, Marco Gaido <
> marcogaid...@gmail.com> wrote:
>
>
> Yes, you're right Herman. Sorry, my bad.
>
> Thanks.
> Marco
>
> 2018-06-13 14:01 GMT+02:00 Herman
Unsubscribe
On Thu, Jun 14, 2018 at 8:38 PM Kumar S, Sajive
wrote:
> Unsubscribe
>
I agree, I dont see pressing need for major version bump as well.
Regards,
Mridul
On Fri, Jun 15, 2018 at 10:25 AM Mark Hamstra wrote:
>
> Changing major version numbers is not about new features or a vague notion
> that it is time to do something that will be seen to be a significant
>
Changing major version numbers is not about new features or a vague notion
that it is time to do something that will be seen to be a significant
release. It is about breaking stable public APIs.
I still remain unconvinced that the next version can't be 2.4.0.
On Fri, Jun 15, 2018 at 1:34 AM Andy
+1 for doing a 2.1.3 release.
Tom
On Wednesday, June 13, 2018, 7:28:26 AM CDT, Marco Gaido
wrote:
Yes, you're right Herman. Sorry, my bad.
Thanks.Marco
2018-06-13 14:01 GMT+02:00 Herman van Hövell tot Westerflier
:
Isn't this only a problem with Spark 2.3.x?
On Wed, Jun 13, 2018 at
Hi,
I would like to briefly present you my use case and gather possible useful
suggestions from the community. I am developing a spark job which massively
read from and write to Hive. Usually, I use 200 executors with 12g memory
each and a parallelism level of 600. The main run of the application
Hello,
I’m sorry to bother you again but it is quite important for us to understand
the problem better.
One more finding in our problem is that the performance of queries in a
timestamp sorted file depend a lot on the predicate timestamp.
If you are lucky to get some records from the start of
*Dear all:*
It have been 2 months since this topic being proposed. Any progress now?
2018 has been passed about 1/2.
I agree with that the new version should be some exciting new feature. How
about this one:
*6. ML/DL framework to be integrated as core component and feature. (Such
as Angel /
Unsuscribe
2018-06-15 9:20 GMT+02:00 stc :
> The repo you give may solve some of SqlStreaming problems, but not
> friendly enough, user need to learn this new syntax.
>
> --
> Jacky Lee
> Mail：qcsd2...@163.com
>
> At 2018-06-15 11:48:01, "Bowden, Chris"
> wrote:
>
> Not sure if there is a
The repo you give may solve some of SqlStreaming problems, but not friendly
enough, user need to learn this new syntax.
--
Jacky Lee
Mail：qcsd2...@163.com
At 2018-06-15 11:48:01, "Bowden, Chris" wrote:
Not sure if there is a question in here, but if you are hinting that structured
12 matches
Mail list logo
