[
https://issues.apache.org/jira/browse/BEAM-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17250098#comment-17250098
]
Kenneth Knowles commented on BEAM-10222:
----------------------------------------
Yes, as of 2.26.0 there is no dependency on JDK's faulty guess at number of
CPUs available, regardless of docker.
> Dataflow sets CPU limits on docker containers near zero so Java 11 only
> detects 1 CPU
> -------------------------------------------------------------------------------------
>
> Key: BEAM-10222
> URL: https://issues.apache.org/jira/browse/BEAM-10222
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Mikhail Gryzykhin
> Assignee: Kenneth Knowles
> Priority: P2
> Fix For: 2.26.0
>
>
> When specifying the worker-type as "n1-highcpu-4" the resulting thread number
> is 4 when the pipeline is compiled by Java8, and only 1 when the pipeline is
> compiled by Java11.
> Specifying numberOfWorkerHarnessThreads does not change amount of detected
> threads.
> Amount of available CPUs is received via
> "Runtime.getRuntime().availableProcessors()"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
