V8.0.12 Garbage Collection

Hey Guys,

I just installed V8.0.12 on an Azure Windows Server 2019 Datacenter and noticed that the Garbage Collectors are different to what I see when installing the same version on a Windows 10 VM. Is there something I am missing that may cause Ignition to revert to one or the other?

Windows server 2019

image

Windows 10 G1GC as I have normally encountered.

image

Many Thanks

Tim

If you restore a gateway backup from v7.9.x, it’s default ignition.conf file would still have the CMS collector. Compare the two server’s ignition.conf files.

1 Like

Thanks for the reply,

The Installs have been done without restoring any V7.9 backups.

Looking at the conf files from each they are pretty much identical with the Java Additional Parameters section not showing anything to do with G1GC as it would with V7.9 as below.

# Java Additional Parameters
wrapper.java.additional.3=-Ddata.dir=data
#wrapper.java.additional.2=-Xdebug
#wrapper.java.additional.3=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=*:8000

I did a quick test and inserted the below and restarted the gateway and G1GC came back.

# Java Additional Parameters
wrapper.java.additional.1=-XX:+UseG1GC
wrapper.java.additional.2=-XX:MaxGCPauseMillis=200
wrapper.java.additional.3=-Ddata.dir=data
#wrapper.java.additional.2=-Xdebug
#wrapper.java.additional.3=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=*:8000

Cheers

1 Like