Ok, thanks for explanation. Is it possible to make the garbage collection process more efficient / faster - e.g. with tuning -Xms / -Xmx parameters in java (during the start of NIS) ?
Well, I think G1GC is the garbage collector that has less “stop the world” events. But even with that one some times full garbage collections are necessary and those events bring the server to a halt for 15 seconds (depending on how much ram your server has).
So the bigger memory the faster that garbage process could be ? So it’s good idea to try to increase -Xms (initial heap) and especially -Xmx (memory allocation pool), if I have some other part of whole RAM still available ?
No, the more memory the server has, the longer it will take until the first full GC occurs, but the full GC will also take longer since more memory means more work doing a full GC.
I don’t know what influence the Xms param has on the full GC timing. I personally always set Xms equal to Xmx.
Hi,
supernode 88.99.87.132 “croissant”
is going down on maintenance now.
Harvesters should reactivate.
1 Like
All Supernode owners please upgrade to V0.6.97. The upgrade is mandatory.
On 2019-04-28 there will be database maintenance. After the database is up again, all supernodes are required to run V0.6-97. Subsequent version tests hereafter with versions prior to 0.6.97 will fail!
3 Likes
我申请：
I apply:
Change ip 45.248.86.23 to 23.236.76.15
Change alias pvkpnem to pvknem001
Hi. Please change IP of my supernode.
Change ip 45.248.86.23 to 23.236.76.15
Change alias pvkpnem to pvknem001
I already sent enroll message to NAFUND address,
the tx hash:
98255a129ca99e3586497081827813fe054f6b6cd40c203d77d99c92dd3e396a
Thanks!
Hi. Please change IP of my another supernode.
Change ip 47.105.108.134 to 167.88.178.31
I already sent enroll message to NAFUND address,
the tx hash:
5a1f82069fc08cb338f9ce2d4a4ad3c7d3f21f1a478dda7d471b36f497076e99
Thanks!
Is NEM still under development? Any future updates? 
NIS is not developed any more, only bugs are removed if found. Development has shifted to Catapult.
Some of these fails may be intermittent, try monitoring it for a few days and see if you notice any change. Failing that try a reboot. Possible could be more ram needed.
Usually means that the supernode does not have enough RAM and thus was unable keep up with the chain.
thank you!
If I upgrade to 8G memory, The nix.runNis.sh will be as follow:
#!/bin/bash
cd nis
java -Xms2800M -Xmx2800M -cp “.:./:…/libs/” org.nem.deploy.CommonStarter -XX:+UseG1GC -XX:MaxGCPauseMillis=200
cd -
Is it Right ?
Hi. Please change IP of my supernode.
Change ip 185.238.249.193 to 167.88.177.45
I already sent enroll message to NAFUND address,
the tx hash:
d72aea25dc78e59c6974c2ea5c9367f499f2d85599ac3b7d56cb6f76bb25447f
Thanks!
With 8GB memory it should like
java -Xms5G -Xmx5G -cp “.:./ *:…/libs/* ” org.nem.deploy.CommonStarter -XX:+UseG1GC -XX:MaxGCPauseMillis=200
Done.
The second node ：
Hi. Please change IP of my supernode.
Change ip 167.88.178.31 to 167.88.177.116
I already sent enroll message to NAFUND address,
the tx hash:
891d81a3015ebb57aceef8c1c4eecfa5e7419118c49150418f5f2e449dbd5fe1
Thanks!