Hi,
Will it be possible to provide the server logs so we can tell better what is going on here?
If you start the server with "-initial-heap" and "-max-heap" options then resource manager is setup and it should not give an OOME as long as the tables have overflow to disk configured. Usually one would use LRUHEAPPERCENT as the eviction criterion which means that when the heap reaches a threshold then data from table will be evicted to disk where the threshold is by default at 72% when using -initial-heap+max-heap options or as explicitly set by heap eviction config procedures.
For example:
CREATE TABLE ... (
...
)
EVICTION BY LRUHEAPPERCENT EVICTACTION OVERFLOW
PERSISTENT ASYNCHRONOUS
which specifies async persistence with overflow when heap hits the threshold as mentioned before.
Since SQLFire is memory-optimized db, so it will not overflow to disk unless it is mentioned in create table explicitly. Currently indexes are always in memory, so one needs to plan for that much of capacity (this will be addressed in coming releases). See more on this here.
In this case if startup is failing due to not enough memory, you can use the initial-heap/max-heap options to increase heap size and let the tables configured with LRUHEAPPERCENT eviction to overflow to disk.
thanks
sumedh