Hi Alex, 1. Pre-touch will not save from killing node by OS if there will not enough memory for JVM internal needs, anyway. Ignite data region setting has MIN and MAX sizes. Ignite split memory region into segments, first segment is size of MIN. Next segments are allocated on demand (up to MAX) and have size of 256Mb.
AFAIK, Ignite always pre-touch first region. So, you can try to set region MAX size equal to MIN and get region allocated on node start. Do you mean this is not work as expected? 2. We try to add off-heap size checks in configuration validation procedure. On Thu, Oct 25, 2018 at 5:41 PM Gerus <age...@gridgain.com> wrote: > Hi, Ivan > Let me try to explain. I think that there are 2 goals that are mostly > applicable for prod systems: > 1. I can agree with Dave that swap is not a good case for performance and > disk resource. It is possible that other applications can consume memory > that is free after Ignite was started. In this case if Ignite will be > creating new pages in runtime, it can face with OOM. > > 2. Ignite user can create wrong configuration. For example, data region can > exceed available memory by mistake or Ignite can be started on another > server with less RAM. It can lead to catch OOM in runtime > > To summarize: Pre-allocation can detect listed issues on Ignite start by > allocating OS RAM > > Im sure that this option have to be disabled by default, but user should > have a choice for startup > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > -- Best regards, Andrey V. Mashenkov
