Hello! Regarding PME problems. OOM will cause this. High GC could cause this under some circumstances. High CPU or Disk usage should not cause this. Network inavailability (such as closed communication port) could also cause it.
But the prime cause is programming errors. Either those are errors on Apache Ignite side (caused by some strange circumstances since all normal cases should be normally tested), or they are in your code. Such as deadlocks. If you have deadlocks in your code exposed to Apache Ignite, or you are manage to lock up Apache Ignite in other ways (listeners, invokes and continuous queries are notorious for that, since there are limitations on operations you can use from within them), you can catch infinite PME very easily. However, it's hard to say without reviewing logs and thread dumps./ Regards, -- Ilya Kasnacheev чт, 13 сент. 2018 г. в 1:31, ndipiazza3565 <[email protected] >: > I'm trying to build up a list of possible causes for this issue. > > I'm only really interested in the issues that occur after successful > production deployments. Meaning the environment has been up for some time > successfully, but then later on our ignite nodes will not start and stick > > But as of now, a certain bad behavior from a single node in the ignite > cluster can cause a deadlock > > * Anything that causes one of the ignite nodes to become unresponsive > * oom > * high gc > * high cpu > * high disk usage > * Network issues? > > I'm trying to get a list of the causes for this issue so I can troubleshoot > further. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
