Thanks! It works.
On Wed, Oct 17, 2018 at 4:46 PM Stanislav Lukyanov
wrote:
> Put your -X* options before -jar. That’s how java command line works.
>
>
>
> Stan
>
>
>
> *From: *Lokesh Sharma
> *Sent: *17 октября 2018 г. 14:08
> *To: *user@ignite.apache.org
>
Put your -X* options before -jar. That’s how java command line works.
Stan
From: Lokesh Sharma
Sent: 17 октября 2018 г. 14:08
To: user@ignite.apache.org
Subject: Re: Ignite complains for low heap memory
I get the same output in the logs when I run the application with Xms set to 2
GB. I ran
I get the same output in the logs when I run the application with Xms set
to 2 GB. I ran this command:
java -jar target/cm.jar -Xms2024m -Xmx4024m
On Wed, Oct 17, 2018 at 4:26 PM aealexsandrov
wrote:
> Hi,
>
> The heap metrics that you see in topology message shows the max heap value
> that yo
Hi,
The heap metrics that you see in topology message shows the max heap value
that your cluster can use:
Math.max(m.getHeapMemoryInitialized(), m.getHeapMemoryMaximum()
Initial heap size (-Xms ) is different from the maximum (-Xmx). Your JVM
will be started with Xms amount of memory and will be
*Typo Correction: The later heap size is 2.6 GB not 2 GB.
On Wed, Oct 17, 2018 at 3:53 PM Lokesh Sharma
wrote:
> When Ignite boots up, it initially complains that only "188 MB is
> available":
>
> 2018-10-17 15:44:12.295 WARN 15129 --- [pub-#22%cm%]
>> o.apache.ignite.internal.GridDiagnosti
When Ignite boots up, it initially complains that only "188 MB is
available":
2018-10-17 15:44:12.295 WARN 15129 --- [pub-#22%cm%]
> o.apache.ignite.internal.GridDiagnostic : Initial heap size is 188MB
> (should be no less than 512MB, use -Xms512m -Xmx512m).
> [15:44:12] Initial heap size is
