Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.1 Bedienungsanleitung PDF herunterladen (Seite 11)

5. Turn the second node back on.

6. Use the service relocate command to move one of the instances of Caché back to the

second node.

7. Try to connect the System Management Portal to the two instances of Caché using the

cluster virtual IP addresses. Look at the server and instance names in the title bar to

determine which node you have connected to and click About to see the path name to the

cache.cpf ﬁle.

4.1 Caché Initialization File for Linux

This section shows a sample script to start and stop Caché on the Red Hat Enterprise Linux

AS. Save the ﬁle as /etc/rc.d/init.c/cache or /usr/local/etc/cachesys/cache-init and set the pro-

tection to 755. The sample script:

#!/bin/ksh

# cache

# Cache "System V init" script for Linux systems

# Confidential, unpublished property of InterSystems.

# ------------------------------------------------------------------

# This script is put in the init.d directory and is used by

# the HA failover package to start a Cache instance when

# the node that was "serving" it failed.

# Three arguments should be specified:

# hacache start <inst name> failover

# where <inst name> is the name of the instance that

# is displayed by "/usr/bin/ccontrol all" in the 2nd column.

# This script can be used to start Cache if Cache is currently

# down (meaning it is down on both nodes).

# On failover, it removes the .ids file. If it is not in failover,

# it tries to restart Cache anyway. If the node trying to start

# Cache was the node it was last running on (for example, the cluster

# is rebooting) then it will succeed. If not, it will fail.

# When it fails it could be because Cache is running on the other node

# or it could be that it was running on the other node when the cluster

# crashed and now we're attempting startup on a different node,

# in which case the .ids file either needs to be manually removed or the

# service needs to be started on the other node.

# It is very dangerous to call this script and specify the failover

# flag outside of the failover scripts. In an HA environment where

# multiple nodes can see the attached storage simultaneously (eg. NFS

# mounted file systems) it is possible to start Cache from the same

# directory on both nodes; Cache does not currently prevent this.

# If this occurs the results will be disasterous and both nodes will

# have to be shut down, database degradation may need to be repaired,

# and so on.

Caché ECP Clusters on Red Hat Enterprise Linux 7

Adding Caché to the Cluster Services

1 2 ... 6 7 8 9 10 11 12 13 14

Kommentare zu diesen Handbüchern

Keine Kommentare

Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.1 Bedienungsanleitung Seite 11

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Server Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.1