You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/11/20 17:12:02 UTC

[jira] [Commented] (BEAM-10222) Dataflow sets CPU limits on docker containers near zero so Java 11 only detects 1 CPU

    [ https://issues.apache.org/jira/browse/BEAM-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236301#comment-17236301 ] 

Beam JIRA Bot commented on BEAM-10222:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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
>              Labels: stale-assigned
>
> 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)