[
https://issues.apache.org/jira/browse/SPARK-30556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022273#comment-17022273
]
Dongjoon Hyun commented on SPARK-30556:
---------------------------------------
Thank you for confirming, [~ajithshetty].
This is backported to branch-2.4 via https://github.com/apache/spark/pull/27340
> Copy sparkContext.localproperties to child thread
> inSubqueryExec.executionContext
> ---------------------------------------------------------------------------------
>
> Key: SPARK-30556
> URL: https://issues.apache.org/jira/browse/SPARK-30556
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.3.4, 2.4.4, 3.0.0
> Reporter: Ajith S
> Assignee: Ajith S
> Priority: Major
> Fix For: 2.4.5, 3.0.0
>
>
> Local properties set via sparkContext are not available as TaskContext
> properties when executing jobs and threadpools have idle threads which are
> reused
> Explanation:
> When SubqueryExec, the {{relationFuture}} is evaluated via a separate thread.
> The threads inherit the {{localProperties}} from sparkContext as they are the
> child threads.
> These threads are controlled via the executionContext (thread pools). Each
> Thread pool has a default {{keepAliveSeconds}} of 60 seconds for idle threads.
> Scenarios where the thread pool has threads which are idle and reused for a
> subsequent new query, the thread local properties will not be inherited from
> spark context (thread properties are inherited only on thread creation) hence
> end up having old or no properties set. This will cause taskset properties to
> be missing when properties are transferred by child thread via
> {{sparkContext.runJob/submitJob}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
