park-user-list.1001560.n3.nabble.com/
>> file/n27910/profiler.png>
>>
>> Since each test suite passes when running by itself,
>> I think that the broadcasts are leaking between the tests suites.
>>
>> Any suggestions on how to resolve this?
>>
>&
n running by itself,
> I think that the broadcasts are leaking between the tests suites.
>
> Any suggestions on how to resolve this?
>
> thanks
>
>
>
>
>
> --
> View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Possible-memory
ist.1001560.n3.nabble.com/Possible-memory-leak-after-closing-spark-context-in-v2-0-1-tp27910.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
-
To unsubscribe e-mail: user-unsubscr...@spark.apache.org
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Possible-memory-leak-tp26478.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: user-unsubscr...@sp
Problem we're seeing is a gradual memory leak in the driver's JVM.
Executing jobs using a long running Java app which creates relatively
short-lived SparkContext's. So our Spark drivers are created as part of
this application's JVM. We're using standalone cluster mode, spark 1.0.2
Root cause of t
