[ 
https://issues.apache.org/jira/browse/SPARK-25901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Apache Spark reassigned SPARK-25901:
------------------------------------

    Assignee:     (was: Apache Spark)

> Barrier mode spawns a bunch of threads that get collected on gc
> ---------------------------------------------------------------
>
>                 Key: SPARK-25901
>                 URL: https://issues.apache.org/jira/browse/SPARK-25901
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.4.0
>            Reporter: yogesh garg
>            Priority: Major
>         Attachments: Screen Shot 2018-10-31 at 11.57.25 AM.png, Screen Shot 
> 2018-10-31 at 11.57.42 AM.png
>
>
> After a barrier job is terminated (successfully or interrupted), the 
> accompanying thread created with `Timer` in `BarrierTaskContext` shows in a 
> waiting state until gc is called. We should probably have just one thread to 
> schedule all such tasks, since they just log every 60 seconds.
> Here's a screen shot of the threads growing with more tasks:
>  !Screen Shot 2018-10-31 at 11.57.25 AM.png! 
> Here's a screen shot of constant number of threads with more tasks:
>  !Screen Shot 2018-10-31 at 11.57.42 AM.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to