Auto resending after a failover (on the receiving side)

If a failover occurs while receiving (data transfer), an auto resending is carried out on the STANDBY node that takes over the operation.

HULFT on the sending side is notified that an auto resending (on the receiving side) should be carried out. If the failover occurs on the receiving side, an auto resending (on the receiving side) is carried out only when the Receive process is terminated unsuccessfully by the termination synchronization function (in Forced Stop mode).

= Remarks =

  • 591-000 is the error code of HULFT on the receiving side for which the auto resending (on the receiving side) is carried out after the failover.

  • For details on HULFT on the sending side that supports auto resending after a failover (on the receiving side), refer to Notes on auto resending after a failover (receiving side).

Figure 2.9 Auto Resending After Failover (on Receiving Side)

1) Error Detection

The clustering software detects an error in a cluster (or within the group where a failover occurs).

2) Forced stop of the Receive daemon

HULFT on the receiving side (ACTIVE node) stops the process while receiving by using the termination synchronization function (in Forced Stop mode), and then stops the Receive daemon.

3) Notification to HULFT on the sending side

HULFT on the receiving side notifies HULFT on the sending side that the processing has been terminated in Forced Stop mode due to an error and disconnects the connection from HULFT on the sending side.

4) Failover

The processing is taken over by the STANDBY node from the ACTIVE node.

5) Receive daemon startup

The Start Synchronization function starts the Receive daemon on the node that has taken over the operation.

6) Connection to HULFT on the receiving side

HULFT on the sending side connects to HULFT on the receiving side (STANDBY node) after the time that is set for Connect Retry Interval (retrytime) in the System Environment Settings expires and then carries out a file transfer (auto resending (on the receiving side)).

7) Auto resending after failover (on the receiving side)

If an auto resending is carried out from HULFT on the sending side, HULFT on the receiving side carries out receiving after a failover occurs.

HULFT on the sending side repeats steps 1) through 6) the number of times set for Auto Resend Retry Count (sockerr_autoretry) in the System Environment Settings.