[
https://issues.apache.org/jira/browse/IGNITE-23085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Davydov updated IGNITE-23085:
------------------------------------
Description:
There are cases, when the specified memory for Ignite (Heap, Data Regions ...)
is not enough for correct and robust cluster performance. This case is checked
at the startup and the corespoding WARNING is issued in the log.
Nevertheless the log message is not very informative for the user, as it is
hard to understand why the specified amount is insufficient.
To work this issue out, I propose to add more information to the log message.
It might help user to configure memory carefully in case the node crushes.
Changes:
* Informative Warn message.
was:
There are cases, when the specified memory for Ignite (Heap, Data Regions ...)
is not enough for correct and robust cluster performance. This case is checked
at the startup and the corespoding WARNING is issued in the log.
Nevertheless the log message is not very informative for the user, as it is
hard to understand why the specified amount is insufficient.
To work this issue out, I propose to add more information to the log message.
It might help user to configure memory carefully in case the node crushes.
Changes:
* Informative Warn message.
* Required memory shouldn't exceed the physical RAM.
> Out of Memory preventive actions at startup
> -------------------------------------------
>
> Key: IGNITE-23085
> URL: https://issues.apache.org/jira/browse/IGNITE-23085
> Project: Ignite
> Issue Type: Improvement
> Reporter: Maksim Davydov
> Assignee: Maksim Davydov
> Priority: Trivial
> Labels: ise, newbie
> Fix For: 2.17
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are cases, when the specified memory for Ignite (Heap, Data Regions
> ...) is not enough for correct and robust cluster performance. This case is
> checked at the startup and the corespoding WARNING is issued in the log.
> Nevertheless the log message is not very informative for the user, as it is
> hard to understand why the specified amount is insufficient.
> To work this issue out, I propose to add more information to the log message.
> It might help user to configure memory carefully in case the node crushes.
> Changes:
> * Informative Warn message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
