unsurprisingly, we had another GC: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70949/console
so, definitely not the system (everything looks hunky dory on the build node). > It can always be some memory leak; if we increase the memory settings > and OOMs still happen, that would be a good indication. Also if the > same tests tend to fail (even if unreliably). > yeah, this would be a great way to check for leaks. :) > Normally some existing code / feature requiring more memory than > before, especially some non-trivial amount, is suspicious. But > sometimes new features / new tests require more memory than configured > in the build scripts, and sometimes blow up. > yep... i agree on both points. --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
