This section contains information about configuring the
group buffer pool and cluster
caching facilities,
and changing the cluster file system quorum type. Generally speaking,
most of these tasks are only necessary in certain circumstances.
Creating a shared file system
Once you have created a DB2 pureScale instance,
you must create the file systems for the database directories and
log files, before you create a database.
DB2 pureScale Feature cluster caching facility configuration
In a DB2 pureScale environment, the cluster caching facility, also known as CF, is used to facilitate global locking and buffer pool
management. CF configuration is integrated into DB2 infrastructure and managed by DB2 configuration interfaces.
Changing the cluster manager quorum type
The DB2 cluster
services tiebreaker
is set up initially in the installation GUI when the first instance
is created. Change the cluster manager quorum type only if a problem
occurs with the specified disk or the configuration changes.
Changing the shared file system quorum type
The shared file system quorum type is assigned automatically
during the setup of the IBM® DB2 pureScale Feature. Because
the quorum type selected is based upon the number of hosts in the
cluster, you must change the quorum type after adding or removing
hosts from the DB2 instance.
Changing the host failure detection time
Fast failure detection is crucial to a DB2 pureScale instance because the faster a host failure is detected,
the earlier the recovery for the failure can begin. That said, an
aggressive setting for the host failure detection time is not suited
for high-latency environments, so users might want to adjust the setting.
Buffer pools in a DB2 pureScale environment
In a DB2 pureScale environment, the cluster caching facility provides
a common group buffer pool (GBP) that is shared by all members.
Each member also
manages its own set of local buffer pools (LBPs).
Self-tuning memory in a DB2 pureScale environment
When self-tuning
memory is enabled in a DB2 pureScale environment,
the tuning member monitors
the memory configuration and propagates any configuration changes
to all other members.