Oracle® Solaris Cluster Concepts Guide

Exit Print View

Updated: July 2014, E39575-01
 
 

SPARC: Dynamic Reconfiguration Clustering Considerations for Memory

    For the purposes of dynamic reconfiguration, there are two types of memory:

  • Kernel memory cage

  • Non-kernel memory cage

These two types differ only in usage. The actual hardware is the same for both types. Kernel memory cage is the memory that is used by the Oracle Solaris Operating System. Careful consideration must be taken before performing a dynamic reconfiguration remove-board operation which will impact kernel memory cage. Oracle Solaris Cluster software does not reject the operation, but in most cases, such a dynamic reconfiguration operation will have a significant impact on the entire cluster. The tight coupling between cluster nodes, between multiple instances of scalable applications, and between the primary and secondary nodes of HA applications and services means that the quiescing of one node for repair can cause operations on non-quiesced nodes to be delayed until the repair operation is complete and the node is unquiesced.

In most cases, the preferred method of removing or replacing a system board with kernel cage memory is to bring the node requiring repair down. This allows the remainder of the cluster to cleanly take over the duties of the node being repaired. Only when circumstances prevent the node requiring repair from being brought out of the cluster, should dynamic reconfiguration be used to remove or replace a system board with kernel cage memory while the node is still part of the operating cluster. For suggestions on preparing the cluster for a dynamic reconfiguration kernel cage remove-board operation, see Preparing the Cluster for Kernel Cage Dynamic Reconfiguration in Oracle Solaris Cluster 4.2 Hardware Administration Manual .

When a dynamic reconfiguration add-board operation that pertains to memory succeeds, memory on the added board is automatically incorporated in system operation.

If the node being repaired panics during the dynamic reconfiguration operation, or if the dynamic reconfiguration operation is otherwise interrupted, it may be necessary to manually re-enable heartbeat monitoring and reset the repaired node's quorum vote count. These two actions are normally done automatically at the completion of the dynamic reconfiguration operation to return the cluster to a stable state. For instructions on recovering in this case, see How to Recover From an Interrupted Kernel Cage Dynamic Reconfiguration Operation in Oracle Solaris Cluster 4.2 Hardware Administration Manual .