[
https://issues.apache.org/jira/browse/SPARK-22590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajith S updated SPARK-22590:
----------------------------
Summary: Broadcast thread propagates the localProperties to task (was:
SparkContext's local properties missing from TaskContext properties)
> Broadcast thread propagates the localProperties to task
> -------------------------------------------------------
>
> Key: SPARK-22590
> URL: https://issues.apache.org/jira/browse/SPARK-22590
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.2.0
> Reporter: Ajith S
> Priority: Major
> Labels: bulk-closed
> Attachments: TestProps.scala
>
>
> Local properties set via sparkContext are not available as TaskContext
> properties when executing parallel jobs and threadpools have idle threads
> Explanation:
> When executing parallel jobs via {{BroadcastExchangeExec}}, the
> {{relationFuture}} is evaluated via a seperate 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}}
> Attached is a test-case to simulate this behavior
--
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
