Thanks! Wasn't aware of these!
On Fri, Jun 22, 2018 at 7:14 AM, David Wimsey wrote:
> Are you enabling the extra flags required for the JVM work detect memory
> and work properly?
>
> Specifically adding the following options to the JVM options when starting
> ignite
>
> -XX:+UseCGroupMemoryLimi
One node per container. Configuration below, key values come from env vars.
IGNITE_DATA_REGION_MAX_SIZE_MB=16384
IGNITE_DATA_REGION_MAX_SIZE=$(( $PIPE_IGNITE_DATA_REGION_MAX_SIZE_MB * 1024
* 1024 )) # 17179869184
IGNITE_JVM_OPTS='-Xms8g -Xmx8g'
IGNITE_PERSISTENCE_ENABLED=true
IGNITE_TEST_CACHE_BA
Are you enabling the extra flags required for the JVM work detect memory and
work properly?
Specifically adding the following options to the JVM options when starting
ignite
-XX:+UseCGroupMemoryLimitForHeap. The -XX:+UnlockExperimentalVMOptions
See:
https://blogs.oracle.com/java-platform-grou
Hi,
Could you please provide your configuration files? How many nodes did you
start in your container?
BR,
Andrei
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I can see from the docs for IgniteConfiguration that some properties
auto-size based on visible OS resources. In docker, "visible" ends up being
the host values, which will exceed any CPU/memory limits applied via
cgroups to the container.
I see on
IgniteConfiguration.DataStorageConfiguration.Data
