We are running Ignite in LOCAL mode with persistence enabled. For large putAll 
calls with low off-heap memory enabled, we are able to trigger OOM exceptions, 
which is something that is being investigated separately. When these exceptions 
occur and our process is run again, it hangs when calling Ignite.active(). I 
tried commenting this out and it also hangs when calling 
Ignite.getOrCreateCache. Either way, the normal workflow is to call 
Ignite.active on startup. Why does this hang if an exception causes the process 
to crash?

Reply via email to