This slide describes the functionality of the new
FastStartFailoverLagLimit configuration property.
When no synchronous standby destinations are available, a standby that uses asynchronous redo transport can be used as a fast-start failover target provided the
FastStartFailoverLagLimit configuration property is set. When a synchronous standby becomes available, the broker automatically switches back to the synchronous standby.
FastStartFailoverLagLimit configuration property establishes an acceptable limit, in seconds, that the standby is allowed to fall behind the primary in terms of redo applied. If the limit is reached, then a fast-start failover is not allowed. The lowest possible value is 5 seconds. This property is used when fast-start failover is enabled and the configuration is operating in maximum performance mode.