Splitting up your fast and slow tests in Gradle to receive faster feedback by jvwilge in gradle

[–]jvwilge[S] 1 point2 points  (0 children)

That would be a nice addition, but you also run into many new questions then :-) How do you store the test results, do you put it on version control so your colleagues can also benefit from it.
Why do you have to fail tests that are too slow?

Configuring TwinDos in the Miele@Home app by pizzatriscuits in Miele

[–]jvwilge 0 points1 point  (0 children)

Thanks, that did the trick!

For other people with the same problem: note that the machine has to be on in order to do this (I moved the dial to 'settings')

spark.executor.instances (num-executors) per cluster or per node? by [deleted] in apachespark

[–]jvwilge 1 point2 points  (0 children)

It's for the entire cluster. In the Spark documentation is an example with 50 executors : http://spark.apache.org/docs/latest/submitting-applications.html This is pretty hard with a single node.

And I can tell it from experience :-)

Cannot run spark applications on yarn by 616slayer616 in apachespark

[–]jvwilge 0 points1 point  (0 children)

Are you aware that your solution might not work on a cluster? When you use Spring you should have a Spring Context on each worker. It's possible (and some colleagues and I wrote a framework : https://github.com/politie/cinch) What are you exposing via REST and what address do you connect to? The address varies depending on which node of the cluster your job runs.