Skip to content

Conversation

@JoshRosen
Copy link
Contributor

SparkListenerSuite's "onTaskGettingResult() called when result fetched remotely" test was extremely slow (1 to 4 minutes to run) and recently became extremely flaky, frequently failing with OutOfMemoryError.

The root cause was the fact that this was using System.setProperty to set the Akka frame size, which was not actually modifying the frame size. As a result, this test would allocate much more data than necessary. The fix here is to simply use SparkConf in order to configure the frame size.

@andrewor14
Copy link
Contributor

It already passed the test. Merging into master 1.6.

asfgit pushed a commit that referenced this pull request Nov 18, 2015
SparkListenerSuite's _"onTaskGettingResult() called when result fetched remotely"_ test was extremely slow (1 to 4 minutes to run) and recently became extremely flaky, frequently failing with OutOfMemoryError.

The root cause was the fact that this was using `System.setProperty` to set the Akka frame size, which was not actually modifying the frame size. As a result, this test would allocate much more data than necessary. The fix here is to simply use SparkConf in order to configure the frame size.

Author: Josh Rosen <[email protected]>

Closes #9822 from JoshRosen/SPARK-11649.

(cherry picked from commit 3a98519)
Signed-off-by: Andrew Or <[email protected]>
@asfgit asfgit closed this in 3a98519 Nov 18, 2015
@JoshRosen JoshRosen deleted the SPARK-11649 branch November 18, 2015 23:57
@SparkQA
Copy link

SparkQA commented Nov 19, 2015

Test build #46264 has finished for PR 9822 at commit 1ae1391.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

asfgit pushed a commit that referenced this pull request Nov 19, 2015
SparkListenerSuite's _"onTaskGettingResult() called when result fetched remotely"_ test was extremely slow (1 to 4 minutes to run) and recently became extremely flaky, frequently failing with OutOfMemoryError.

The root cause was the fact that this was using `System.setProperty` to set the Akka frame size, which was not actually modifying the frame size. As a result, this test would allocate much more data than necessary. The fix here is to simply use SparkConf in order to configure the frame size.

Author: Josh Rosen <[email protected]>

Closes #9822 from JoshRosen/SPARK-11649.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants