{"push_id":880391124,"size":1,"distinct_size":1,"ref":"refs/heads/branch-1.4","head":"f5af299ab06f654e000c99917c703f989bffaa43","before":"1df3e823028c0f1e22e2e61f959ef0343355a757","commits":[{"sha":"f5af299ab06f654e000c99917c703f989bffaa43","author":{"email":"b59cd5ce8cb5ae44d26fc6984be1f84cf74771a7@databricks.com","name":"Shixiong Zhu"},"message":"[SPARK-11999][CORE] Fix the issue that ThreadUtils.newDaemonCachedThreadPool doesn't cache any task\n\nIn the previous codes, `newDaemonCachedThreadPool` uses `SynchronousQueue`, which is wrong. `SynchronousQueue` is an empty queue that cannot cache any task. This patch uses `LinkedBlockingQueue` to fix it along with other fixes to make sure `newDaemonCachedThreadPool` can use at most `maxThreadNumber` threads, and after that, cache tasks to `LinkedBlockingQueue`.\n\nAuthor: Shixiong Zhu <shixiong@databricks.com>\n\nCloses #9978 from zsxwing/cached-threadpool.\n\n(cherry picked from commit d3ef693325f91a1ed340c9756c81244a80398eb2)\nSigned-off-by: Shixiong Zhu <shixiong@databricks.com>","distinct":true,"url":"https://api.github.com/repos/ueshin/apache-spark/commits/f5af299ab06f654e000c99917c703f989bffaa43"}]}