[jira] [Updated] (IGNITE-27049) Print current memory configuration into the logs

["Ivan Bessonov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-27049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Bessonov updated IGNITE-27049:
-----------------------------------
    Reviewer: Aleksandr

> Print current memory configuration into the logs
> ------------------------------------------------
>
>                 Key: IGNITE-27049
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27049
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Yury Yudin
>            Assignee: Viacheslav Blinov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.2
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Recently we've seen quite a few issues raised by the customers where nodes fail with various out of memory conditions, especially when running ignite 3 in the kubernetes environment. 
> While having better documentation and fine tuned defaults will make things easier, we also need to make sure current memory configuration is always printed in the very start of the logs. This will make initial analysis of the problem easier and speed up the resolution. 
> Let's have this printed in details at the very start of the node. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)