lukecwik commented on PR #23234: URL: https://github.com/apache/beam/pull/23234#issuecomment-1270367817
> Unfortunately, addWorker is private to ThreadPoolExecutor, so I honestly don't know how to write my own such that it retains scheduling functionality, because anything that submits via schedule() won't grow the pool. I'm going to try some alternate configurations I would approach this by using an unbounded ExecutorService and adding scheduling functionality to it. This way you're just trying to add the 4 methods necessary for scheduling things and the rest of the methods are mostly forwarded to the delegate (need some minor changes to shutdown/shutdownNow). To handle scheduling, you would have one thread responsible for waking up and reading from a priority queue of the things that need to be launched. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
