lukecwik commented on PR #23234: URL: https://github.com/apache/beam/pull/23234#issuecomment-1263864594
> It looks like the scheduled executor doesn't support out of order execution, at least with this configuration. I'd assume this is due to it constraining the number of threads The javadoc for scheduledexecutorservice says that it uses exactly the core pool size: ``` While this class inherits from ThreadPoolExecutor, a few of the inherited tuning methods are not useful for it. In particular, because it acts as a fixed-sized pool using corePoolSize threads and an unbounded queue, adjustments to maximumPoolSize have no useful effect. Additionally, it is almost never a good idea to set corePoolSize to zero or use allowCoreThreadTimeOut because this may leave the pool without threads to handle tasks once they become eligible to run. ``` Can you find an implementation in guava/apache commons-lang/... that allows for an unbounded number of threads? -- 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]
