16.15.2 When a node failure occurs on a slave node

(1) System processing when a node failure occurs on a slave node

When a node failure occurs on a slave node, that slave nodes is separated from the multi-node configuration. The following figure shows the system processing when a node failure occurs on a slave node:

Figure 16‒8: System processing when a node failure occurs on a slave node

Explanation

When a node failure occurs on the slave node hadb03, that slave node is separated from the multi-node configuration. Processing then continues on the remaining nodes hadb01 and hadb02.

To Page Top

(2) Steps taken by the HADB administrator when a node failure occurs

To identify the cause of the node failure, take the action as described in 14.1 Error-handling flow. Take the aforementioned actions on the node where the failure occurred.

Also acquire the following types of troubleshooting information from the node where the failure occurred:

• Use the adbinfoget command to acquire the HADB server's troubleshooting information.

• Use HA Monitor's monts command to acquire HA Monitor's troubleshooting information.

After resolving the cause of the failure, you can return the node that was separated from the multi-node configuration, back to the multi-node configuration. For details about the procedure for returning nodes to a multi-node configuration, see 16.15.3 Returning a node to the multi-node configuration.

Note that nodes are always returned to a multi-node configuration as slave nodes.

To Page Top