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?
Ignite Hanging on startup after OOME
Mitchell Rathbun (BLOOMBERG/ 731 LEX) Mon, 09 Dec 2019 17:05:36 -0800
- Ignite Hanging on startup after OOME Mitchell Rathbun (BLOOMBERG/ 731 LEX)
- Re: Ignite Hanging on startup a... akurbanov
- Re: Ignite Hanging on startup a... Mitchell Rathbun (BLOOMBERG/ 731 LEX)
