[
https://issues.apache.org/jira/browse/IGNITE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157335#comment-16157335
]
ASF GitHub Bot commented on IGNITE-2092:
----------------------------------------
GitHub user max-neverov opened a pull request:
https://github.com/apache/ignite/pull/2619
IGNITE-2092 Switched to the up-to-date java image which has build-in …
…functionality to detect container CPU limitation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/max-neverov/ignite IGNITE-2092
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2619.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2619
----
commit 48b38c147e5c32b9feb693426be6d27ea6191ab6
Author: Maxim Neverov <[email protected]>
Date: 2017-09-07T17:43:41Z
IGNITE-2092 Switched to the up-to-date java image which has build-in
functionality to detect container CPU limitation
----
> 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)
