Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/21402
Another question before I forget about it again: with the current code, if
`chunkFetchHandlerThreads()` is equal or greater the size of the main thread
pool won't that allow the current bad behavior to still exist?
I think Wenchen suggested that that value should be a percentage of the
number of threads for the other pool, which would avoid that problem (as long
as the percentage is < 100). But a check that results in an error or at least a
noisy warning log could at least help users detect a misconfiguration.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
