You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/04/01 15:05:44 UTC
[GitHub] [spark] srowen commented on issue #23826: [SPARK-26914][SQL] Fix
scheduler pool may be unpredictable when we only want to use default pool
and do not set spark.scheduler.pool for the session
srowen commented on issue #23826: [SPARK-26914][SQL] Fix scheduler pool may be unpredictable when we only want to use default pool and do not set spark.scheduler.pool for the session
URL: https://github.com/apache/spark/pull/23826#issuecomment-478617522
I see, @cxzl25 , is that a different problem? If it's thread-local, and the thread sets to the current correct value each time, why would it need to be set to a previous value? (maybe so I just don't know the logic here well). Is "pool == null" a temporary special case?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org