3.5 KiB
3.5 KiB
Disable-the-platform-access-logs-and-most-of-service-logs-on-EU8-for-farm-stabilization_686074621
Introduction
The farm is down due to high I/O activity. To work around this issue, disable the platform access and service logs on EU8.
The scenario to be addressed involves a platform high thread issue caused by excessive log writes. This situation will not trigger a platform restart but has the potential to bring down the entire farm as the platform becomes unresponsive due to an accumulation of pending threads.
This is a farm-level task.
It will keep the log level of the following packages as INFO:
com.hp.maas.platform.services.workflow
com.hp.maas.platform.ems
com.hp.maas.platform.services.notification
com.hp.maas.platform.services.notificationhistory
com.hp.maas.platform.services.mail
Required steps
- Create a patch file named platform-patch.yaml with the following content.
spec: template: spec: containers: - name: itom-xruntime-platform startupProbe: periodSeconds: 30 timeoutSeconds: 60 failureThreshold: 60 initialDelaySeconds: 120 exec: command: - sh - -c - | sed -i "5s/value=\"INFO\"/value=\"OFF\"/" /opt/apache-tomcat/webapps/platform-webapp/WEB-INF/classes/logback.xml && sed -i "s/<Valve className=\"com.microfocus.maas.platform.runtime.CustomAccessLog\"/<\!-- <Valve className=\"com.microfocus.maas.platform.runtime.CustomAccessLog\"/" /opt/apache-tomcat/conf/server*.xml && sed -i "s/OUTGOING_ITEM_COUNT}r \"\/>/OUTGOING_ITEM_COUNT}r \"\/> -->/" /opt/apache-tomcat/conf/server*.xml && sed -i "s/<logger level=\"\${logger.defaultThreshold}\" name=\"com.hp.maas.platform.services.workflow\">/<logger level=\"INFO\" name=\"com.hp.maas.platform.services.workflow\">/g" /opt/apache-tomcat/webapps/platform-webapp/WEB-INF/classes/sync/log-platform-base.xml && sed -i "s/<logger level=\"\${logger.defaultThreshold}\" name=\"com.hp.maas.platform.ems\">/<logger level=\"INFO\" name=\"com.hp.maas.platform.ems\">/g" /opt/apache-tomcat/webapps/platform-webapp/WEB-INF/classes/sync/log-platform-base.xml && sed -i "s/<logger level=\"\${logger.defaultThreshold}\" name=\"com.hp.maas.platform.services.notification\">/<logger level=\"INFO\" name=\"com.hp.maas.platform.services.notification\">/g" /opt/apache-tomcat/webapps/platform-webapp/WEB-INF/classes/sync/log-platform-base.xml && sed -i "s/<logger level=\"\${logger.defaultThreshold}\" name=\"com.hp.maas.platform.services.notificationhistory\">/<logger level=\"INFO\" name=\"com.hp.maas.platform.services.notificationhistory\">/g" /opt/apache-tomcat/webapps/platform-webapp/WEB-INF/classes/sync/log-platform-base.xml && sed -i "s/<logger level=\"\${logger.defaultThreshold}\" name=\"com.hp.maas.platform.services.mail\">/<logger level=\"INFO\" name=\"com.hp.maas.platform.services.mail\">/g" /opt/apache-tomcat/webapps/platform-webapp/WEB-INF/classes/sync/log-platform-base.xml - Apply the patch file on the control plane node.
kubectl patch deploy itom-xruntime-platform -n <namespace> --patch-file platform-patch.yaml - (Optional) If you want to disable the logging file of the platform-offline pod, run this command:
kubectl patch deploy itom-xruntime-platform-offline -n <namespace> --patch-file platform-patch.yaml