Pausing an RLINK will prevent new and already-queued updates from reaching the primary or secondary RLINK. An RLINK that has been paused on the primary is referred to as primary-paused, and must be resumed from the primary. An RLINK that has been paused on the secondary is referred to as secondary-paused, and must be resumed from the secondary.
The KSTATE of an attached and ACTIVE RLINK is CONNECT if the connection with the secondary is currently up. The connection may temporarily go down because of network outages, but will be restored automatically. Primary-pausing the RLINK changes the STATE of the RLINK from ACTIVE to PAUSE, and the KSTATE from CONNECT to ENABLED.
Unlike a primary PAUSE, a secondary PAUSE does not break the network connection between the primary and the secondary. The KSTATE of both the primary and secondary RLINKs will remain in the CONNECT state. The state of both the primary and the secondary RLINK will change from ACTIVE to PAUSE.
A secondary pause can be performed even if the secondary is disconnected from the primary. When the connection is restored, the primary detects that the secondary is paused and will not send updates. Likewise, a secondary resume can be done when the secondary is disconnected. When a connection is reestablished, the primary detects that the secondary is no longer paused and will resume replication.
A primary RLINK has a state of PAUSE if it is primary-paused, secondary-paused, or both. A secondary RLINK with a state of PAUSE must have its secondary_paused flag set.
Below is an example of an primary RLINK in a pause state: