You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2017/11/02 22:03:00 UTC
[jira] [Updated] (IGNITE-6814) Detailed memory consumption on start
and OOM reporting
[ https://issues.apache.org/jira/browse/IGNITE-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda updated IGNITE-6814:
--------------------------------
Description:
Presently Ignite allocates 20% of RAM on a node startup, however, the user doesn't see automatically chosen memory settings. Also, if there a node runs out of RAM and throws an OOM error there are no hints on why this happened and how to fix it.
Suggestions:
* Add {{off-heap}} field to {{Topology Snapshot}} message. The field will accummulate maximum size of all the data regions defined cluster wide:
{code}
Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, off-heap={total_max_offheap_requested}, heap=1.8GB, ]
{code}
* Provide guidelines on how to overcome OOM when it happens. Specify a data region name with all its current parameters and suggest three possible things - tweak maximum memory, setup eviction policies or enable Ignite persistence. All this is covered in official docs: https://apacheignite.readme.io/docs#section-data-regions
was:
Presently Ignite allocates 20% of RAM on a node startup, however, the user doesn't see automatically chosen memory settings. Also, if there a node runs out of RAM and throws an OOM error there are no hints on why this happened and how to fix it.
Suggestions:
* Add {{off-heap}} field to {{Topology Snapshot}} message. The field will accummulate maximum size of all the data regions defined cluster wide
{code}
Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, off-heap={total_max_offheap_requested}, heap=1.8GB, ]
{code}
* Provide guidelines on how to overcome OOM when it happens. Specify a data region name with all its current parameters and suggest three possible things - tweak maximum memory, setup eviction policies or enable Ignite persistence. All this is covered in official docs: https://apacheignite.readme.io/docs#section-data-regions
> Detailed memory consumption on start and OOM reporting
> ------------------------------------------------------
>
> Key: IGNITE-6814
> URL: https://issues.apache.org/jira/browse/IGNITE-6814
> Project: Ignite
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
> Affects Versions: 2.0
> Reporter: Denis Magda
> Priority: Critical
> Labels: usability
> Fix For: 2.4
>
>
> Presently Ignite allocates 20% of RAM on a node startup, however, the user doesn't see automatically chosen memory settings. Also, if there a node runs out of RAM and throws an OOM error there are no hints on why this happened and how to fix it.
> Suggestions:
> * Add {{off-heap}} field to {{Topology Snapshot}} message. The field will accummulate maximum size of all the data regions defined cluster wide:
> {code}
> Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, off-heap={total_max_offheap_requested}, heap=1.8GB, ]
> {code}
> * Provide guidelines on how to overcome OOM when it happens. Specify a data region name with all its current parameters and suggest three possible things - tweak maximum memory, setup eviction policies or enable Ignite persistence. All this is covered in official docs: https://apacheignite.readme.io/docs#section-data-regions
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)