Description of problem: After migration to java 11 some configuration for java GC logging was omitted. Additionally, GC related logs are sent to console.log together with application logs. For clarity they could be logged into dedicated (rotating) file ie. gc.log, plus logging level could configurable so that in various scenarios 'debug' or even 'trace' be available. The detault is 'info' How reproducible: Enable GC verbose logging by setting up ENGINE_VERBOSE_GC=true Actual results: Deprecated jvm start options being used -XX:+PrintGCTimeStamps and -XX:+PrintGCDetails Expected results: -Xlog framework should be used
Gargabe Collector logging in INFO level enabled by default is not expected to have significant impact on overall performance because these events are aggregated and logged once in a while. However, verification against performance test suite is highly recommended.
Verified on: ovirt-engine-4.4.6.6-0.10.el8ev.noarch Steps: 1. echo "ENGINE_VERBOSE_GC=true" >> /etc/ovirt-engine/engine.conf.d/10-setup-java.conf 2. systemctl restart ovirt-engine 3. cat /var/log/ovirt-engine/gc.log Results: gc.log file present with verbose GC information following the default parameters (lines number, etc)
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.