Scroll to navigation

OCF_HEARTBEAT_SAPHAN(7) OCF resource agents OCF_HEARTBEAT_SAPHAN(7)

NAME

ocf_heartbeat_SAPHanaTopologyScaleOut - Analyzes SAP HANA System Replication Topology.

SYNOPSIS

SAPHanaTopologyScaleOut [start | stop | status | monitor | meta-data | validate-all]

DESCRIPTION

This RA analyzes the SAP HANA topology and "sends" all findings via the node status attributes to all nodes in the cluster. These attributes are taken by the SAPHana RA to control the SAP Hana Databases. In addition it starts and monitors the local saphostagent.

1. Interface to monitor a HANA system: landscapeHostConfiguration.py landscapeHostConfiguration.py has some detailed output about HANA system status and node roles. For our monitor the overall status is relevant. This overall status is reported by the returncode of the script: 0: Internal Fatal 1: ERROR 2: WARNING 3: INFO (maybe a switch of the resource running) 4: OK The SAPHanaTopology resource agent will interpret returncodes 1 as NOT-RUNNING (or 1 failure) and returncodes 2+3+4 as RUNNING. SAPHanaTopology scans the output table of landscapeHostConfiguration.py to identify the roles of the cluster node. Roles means configured and current role of the nameserver as well as the indexserver.

2. Interface is hdbnsutil The interface hdbnsutil is used to check the "topology" of the system replication as well as the current configuration (primary/secondary) of a SAP HANA database instance. A second task of the interface is the posibility to run a system replication takeover (sr_takeover) or to register a former primary to a newer one (sr_register).

3. saphostctrl The interface saphostctrl uses the function ListInstances to figure out the virtual host name of the SAP HANA instance. This is the hostname used during the HANA installation.

SUPPORTED PARAMETERS

SID

The SAP System Identifier (SID)

(required, string, no default)

InstanceNumber

The SAP Instance Number

(required, string, no default)

HANA_CALL_TIMEOUT

Define timeout how long a call to HANA to receive information can take. This could be eg landscapeHostConfiguration.py. There are some specific calls to HANA which have their own timeout values. For example the takeover command does not timeout (inf). If the timeout is reached, the return code will be 124. If you increase the timeouts for HANA calls you should also adjust the operation timeouts of your cluster resources.

(optional, string, default "120")

DIR_EXECUTABLE

Path to the SAP Hana Instance executable directory. If not set the RA tries /usr/sap/$SID/$InstanceName/exe. While InstanceName is the string of "HDB" and $InstanceNumber for SAP Hana databases.

(optional, string, no default)

SUPPORTED ACTIONS

This resource agent supports the following actions (operations):

start

Starts the resource. Suggested minimum timeout: 180.

stop

Stops the resource. Suggested minimum timeout: 60.

status

Performs a status check. Suggested minimum timeout: 60.

monitor

Performs a detailed status check. Suggested minimum timeout: 60. Suggested interval: 60.

validate-all

Performs a validation of the resource configuration. Suggested minimum timeout: 5.

meta-data

Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.

methods

Suggested minimum timeout: 5.

EXAMPLE CRM SHELL

The following is an example configuration for a SAPHanaTopologyScaleOut resource using the crm(8) shell:

primitive p_SAPHanaTopologyScaleOut ocf:heartbeat:SAPHanaTopologyScaleOut \

params \
SID=string \
InstanceNumber=string \
op monitor depth="0" timeout="60" interval="60"

EXAMPLE PCS

The following is an example configuration for a SAPHanaTopologyScaleOut resource using pcs(8)

pcs resource create p_SAPHanaTopologyScaleOut ocf:heartbeat:SAPHanaTopologyScaleOut \

SID=string \
InstanceNumber=string \
op monitor depth="0" timeout="60" interval="60"

SEE ALSO

http://clusterlabs.org/

AUTHOR

ClusterLabs contributors (see the resource agent source for information about individual authors)

08/08/2019 resource-agents UNKNOWN