9.9 Checking the Status of InnoDB ReplicaSet

Check information about a ReplicaSet using the ReplicaSet.status() operation. The ReplicaSet.status() operation supports the extended option to get different levels of detail. For example:

• ReplicaSet.status({extended:0}): Provides a regular level of details. Only basic information about the status of the instance and replication is included, in addition to non-default or unexpected replication settings and status.

• ReplicaSet.status({extended:1}): Setting extended to 1 includes Metadata Version, server UUID, replication information such as lag and worker threads, the raw information used to derive the status of the instance, size of the applier queue, value of system variables that protect against unexpected writes and so on.

• ReplicaSet.status({extended:2}): Setting extended to 2 includes important replication related configuration settings, such as encrypted connections, and so on.

The output of ReplicaSet.status(extended=1) is similar to Cluster.status(extended=1), but the main difference is that the replication field is always available because InnoDB ReplicaSet relies on MySQL Replication all the time, unlike InnoDB Cluster which uses it during incremental recovery. For more information on the fields, see Checking a cluster's Status with Cluster.status().