[jira] [Commented] (IGNITE-2092) Ignite does not recognize the right number of CPU cores when running under Docker

["Maxim Neverov (JIRA)" <ji...@apache.org>]

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

Maxim Neverov commented on IGNITE-2092:
---------------------------------------

This bug is not relevant any longer.
According to [this article|https://blogs.oracle.com/java-platform-group/java-se-support-for-docker-cpu-and-memory-limits] java can discover cpu limitation since 8u131.
Ignite uses java:8 image which is [now obsolete|https://hub.docker.com/_/java/] and tagged as 8u111.
I replaced java:8 with openjdk:8 in the root Dockerfile, built it and ran it with --cpuset-cpus="0". Ignite detected cpu limitation successfully (full boot log is attached):

{noformat}
Topology snapshot [ver=1, servers=1, clients=0, CPUs=1, heap=1.0GB]
{noformat}

So my proposal is to switch to newer jdk.

> Ignite does not recognize the right number of CPU cores when running under Docker
> ---------------------------------------------------------------------------------
>
>                 Key: IGNITE-2092
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2092
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
>            Assignee: Eduard Yuzlikeev
>              Labels: newbie
>             Fix For: 2.3
>
>         Attachments: ignite_boot_log.txt
>
>
> Run Ignite under a Docker container.
> Limit Ignite from using all CPUs by way of Docker settings (which internally uses Linux CGROUPS). 
> Ignite will still report that all available CPUs are used ignoring Docker settings.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)