How To
Summary
When a system's CPU load suddenly increases to 100% or near this value, Pacemaker is at risk of starving CPU cycles and begins to perform poorly in managing Db2 resources, effectively putting the cluster at risk of an outage. This guide will list the steps required to give the pacemaker and corosync processes slightly more priority during these high load times.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m3p000000GnyWAAS","label":"High Availability-\u003ECluster Management"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
27 June 2025
UID
ibm17182717