Github user squito commented on the issue:
https://github.com/apache/spark/pull/19893
> The last suspicious big group of threads (at least for me) is
broadcast-exchange.* but as I've seen this is not false positive because the
threadpool never stopped. In BroadcastExchangeExec:141 a new daemon thread pool
created in case of broadcast join which dies when jvm dies. I suggest to solve
this separately.
what do you mean about handling this separately? should it be whitelisted
for now, or should there be another jira for it? It seems fine to me to set it
aside for now, just want to be clear what the next steps are.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
