How to control the scheduler behavior when you restart the Primary after a failover.
The high-availability mode is disabled when the Primary scheduler fails over to the Shadow scheduler.
How the primary scheduler resumes processing events after you restore it depends on the primary failback mode.
To control the behavior of the Primary scheduler after it is restored and restarted,
set “PrimaryFailbackMode” parameter in config.$AUTOSERV file under $AUTOUSER directory.
The “PrimaryFailbackMode” parameter will define the mode the primary scheduler will enter on restart
when it detects the system is currently in a failed over state.
The following values are available for the primary failback mode :
0 = OFF
Specifies that the primary scheduler will shutdown if it detects the system is in a failed over state.
In this mode, the primary scheduler cannot restart while the shadow scheduler processes events.
You must stop the shadow scheduler first and then restart the primary scheduler.
This is the default value.
1 = DORMANT
Specifies that the primary scheduler will enter into dormant state if it detects the system is in a failed over state.
In this case the primary scheduler runs dormant and resumes processing events only when a failback occurs.
The failback occurs when the shadow scheduler fails or when you initiate a manual failback. If a failback occurs because the shadow scheduler fails, high-availability mode is disabled. In this case, return to high-availability mode by restoring the shadow scheduler.
2 = IMMEDIATE
Specifies that the primary scheduler will takeover and resume processing if it detects the system is in a failed over state.
The shadow scheduler will be notified by the primary scheduler to reenter its dormant state.
The same value will need to be configured in the "config.$AUTOSERV" file on the Primary and Shadow nodes.