Re: OOME on 2-node cluster with visor running repeatedly, Ignite 1.9

"nc - Total number of nodes in the grid" count server + client nodes. I can't find metrics for server nodes. I tried to check the heap dump in "mat" and found a large size of TcpCommunicationSpi#recoveryDescs. Does anyone have an idea why this happened? -- View this message in context:

Re: OOME on 2-node cluster with visor running repeatedly, Ignite 1.9

Thanks Andrey, is there an option to monitor the number of server nodes in the grid? I found "nc - Total number of nodes in the grid.", seems counting server + client nodes, correct? -- View this message in context:

Re: OOME on 2-node cluster with visor running repeatedly, Ignite 1.9

Thank Evgenii! By running the `${IGNITE_HOME}/bin/ignitevisorcmd.sh -e="'open -cpath=${IGNITE_HOME}/config/default-config.xml;node'"`, it shows "Ignite node stopped OK" at the end. Is it an indicator of visor stopped properly? We use the visor output to check the number of Ignite servers

Re: OOME on 2-node cluster with visor running repeatedly, Ignite 1.9

Hi tysli2016, You can run connected to cluster visorcmd in background and register an alert. When this alert is triggered, it may call custom user script. More info can be found here: https://apacheignite-tools.readme.io/docs/alerts-configuration -- View this message in context:

Re: OOME on 2-node cluster with visor running repeatedly, Ignite 1.9

Hi, As i see, you run visor in internal mode, so, it creates a node each time. Are you sure that you stop them properly? Why do you need to start new visor each time? Just use already started visor. Evgenii 2017-05-04 11:57 GMT+03:00 tysli2016 : > Got

OOME on 2-node cluster with visor running repeatedly, Ignite 1.9

Got "OutOfMemoryError: Java heap space" with 2-node cluster with a `visor` running repeatedly. The server nodes are running on CentOS 7 inside Oracle VirtualBox VM with the same config: - 2 vCPUs - 3.5GB memory - Oracle JDK 2.8.0_121 `default-config.xml` was modified to use non-default multicast